starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 09:25:54 +03:00

[GH-ISSUE #1032] Issue: Proxy not detected #599

New issue

Closed

opened 2026-03-01 21:44:51 +03:00 by kerem · 10 comments

kerem commented

2026-03-01 21:44:51 +03:00

Owner

Originally created by @caniko on GitHub (Mar 10, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1032

System information

Operating System: Linux
Architecture: x64 (64-bit)
Docker version: 20.10.12
act version: 0.2.25

Expected behaviour

[Release to PyPI/deploy]   ❗  ::error::connect ECONNREFUSED 140.82.121.5:443
[Release to PyPI/deploy]   ❌  Failure - Set up Python 3.8
Error: exit with `FAILURE`: 1

Actual behaviour

Proxy should be detected from my environment variables in /etc/environemnt.

FYI
I don't have this issue when I run docker and/or minikube, but docker-compose.

Workflow

Steps to reproduce

Run act behind proxy

Originally created by @caniko on GitHub (Mar 10, 2022). Original GitHub issue: https://github.com/nektos/act/issues/1032 ## System information - Operating System: Linux - Architecture: x64 (64-bit) - Docker version: 20.10.12 - `act` version: 0.2.25 ## Expected behaviour ```shell [Release to PyPI/deploy] ❗ ::error::connect ECONNREFUSED 140.82.121.5:443 [Release to PyPI/deploy] ❌ Failure - Set up Python 3.8 Error: exit with `FAILURE`: 1 ``` ## Actual behaviour Proxy should be detected from my environment variables in `/etc/environemnt`. **FYI** I don't have this issue when I run `docker` and/or `minikube`, but `docker-compose`. ## [Workflow](https://github.com/SpikeInterface/spikeinterface) ## Steps to reproduce Run `act` behind proxy

kerem

2026-03-01 21:44:51 +03:00

closed this issue
added the
kind/feature-request
label

kerem commented

2026-03-01 21:44:52 +03:00

Author

Owner

@KnisterPeter commented on GitHub (Mar 28, 2022):

@caniko I don't think it's a bug but more a missing feature. Thanks for reporting.

@KnisterPeter commented on GitHub (Mar 28, 2022): @caniko I don't think it's a bug but more a missing feature. Thanks for reporting.

kerem commented

2026-03-01 21:44:52 +03:00

Author

Owner

@caniko commented on GitHub (Mar 28, 2022):

Please get your definitions right. It is a bug.

@caniko commented on GitHub (Mar 28, 2022): Please get your definitions right. It is a [bug](https://en.wikipedia.org/wiki/Software_bug).

kerem commented

2026-03-01 21:44:52 +03:00

Author

Owner

@catthehacker commented on GitHub (Mar 28, 2022):

Hi, it is not a bug. For it to be a bug, we would have to consider local environment (where act is executed), which we do not, and as you might think it is undesired behaviour, it's not that, simply because we never supported proxies.
A bug is a flaw in code, a mistake made by the one who have written the source code (according to your definition) but there never was a mistake of not adding proxy support.

You can currently pass HTTP_PROXY/HTTPS_PROXY via --env/--env-file if needed as a workaround.

@catthehacker commented on GitHub (Mar 28, 2022): Hi, it is not a bug. For it to be a bug, we would have to consider local environment (where `act` is executed), which we do not, and as you might think it is undesired behaviour, it's not that, simply because we never supported proxies. A bug is a flaw in code, a mistake made by the one who have written the source code (according to your definition) but there never was a mistake of not adding proxy support. You can currently pass `HTTP_PROXY`/`HTTPS_PROXY` via `--env`/`--env-file` if needed as a workaround.

kerem commented

2026-03-01 21:44:52 +03:00

Author

Owner

@caniko commented on GitHub (Mar 29, 2022):

As a thought experiment, imagine selling a product, and using the same logic. Do you still think that it is not a bug?

Furthermore, the workaround changes the entire narrative. Thank you.

@caniko commented on GitHub (Mar 29, 2022): As a thought experiment, imagine selling a product, and using the same logic. Do you still think that it is not a bug? Furthermore, the workaround changes the entire narrative. Thank you.

kerem commented

2026-03-01 21:44:52 +03:00

Author

Owner

@KnisterPeter commented on GitHub (Mar 29, 2022):

Unbelievable. This is free software.
Implement and contribute if you need it!

@KnisterPeter commented on GitHub (Mar 29, 2022): Unbelievable. This is free software. Implement and contribute if you need it!

kerem commented

2026-03-01 21:44:52 +03:00

Author

Owner

@caniko commented on GitHub (Mar 29, 2022):

We were having an argument over semantics, and not the merits of free software.

@caniko commented on GitHub (Mar 29, 2022): We were having an argument over semantics, and not the merits of free software.

kerem commented

2026-03-01 21:44:52 +03:00

Author

Owner

@KnisterPeter commented on GitHub (Mar 29, 2022):

You are nitpicking. As I've said, if you want to have proxy support you can implement it.
It is a missing features as it was never on our roadmap and there is no short term plan to implement it. We simply don't have the capacity and the need to.

@KnisterPeter commented on GitHub (Mar 29, 2022): You are nitpicking. As I've said, if you want to have proxy support you can implement it. It is a missing features as it was never on our roadmap and there is no short term plan to implement it. We simply don't have the capacity and the need to.

kerem commented

2026-03-01 21:44:52 +03:00

Author

Owner

@caniko commented on GitHub (Mar 29, 2022):

Furthermore, the workaround changes the entire narrative. Thank you.

Did you read my last message before closing the issue? I implied that the --env method is fine for me.

@caniko commented on GitHub (Mar 29, 2022): > Furthermore, the workaround changes the entire narrative. Thank you. Did you read my last message before closing the issue? I implied that the `--env` method is fine for me.

kerem commented

2026-03-01 21:44:52 +03:00

Author

Owner

@KnisterPeter commented on GitHub (Mar 29, 2022):

Just to make this even more obvious: you closed the issue 😉

@KnisterPeter commented on GitHub (Mar 29, 2022): Just to make this even more obvious: you closed the issue :wink:

kerem commented

2026-03-01 21:44:52 +03:00

Author

Owner

@helozjisky commented on GitHub (May 29, 2022):

Put this in ~/.actrc should work correctly
--env http_proxy=http://{ip:port}
--env https_proxy=http://{ip:port}

@helozjisky commented on GitHub (May 29, 2022): Put this in ~/.actrc should work correctly --env http_proxy=http://{ip:port} --env https_proxy=http://{ip:port}

kerem referenced this issue

2026-03-01 21:51:31 +03:00

[PR #600] [MERGED] Refactor .actrc locations and default image survey #1517

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#599

No description provided.

Rows
Columns