You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems container-options from .actrc is not propagated to the container specified in container:.
I have a case where all traffic locally needs to go via a proxy when connected to VPN, this proxy also needs custom certificates to be used. This can be solved by:
However, this is used with the main act runner, however it is not propagated to the image used by container.
I can get it working by explicitly adding it to the container configuration inside the workflow, but then it breaks on GitHub that potentially cannot inject this SSL certificate.
I would also need to pass env variables http_proxy, https_proxy and no_proxy.
Any idea if it is possible to pass options to these containers?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It seems container-options from .actrc is not propagated to the container specified in
container:
.I have a case where all traffic locally needs to go via a proxy when connected to VPN, this proxy also needs custom certificates to be used. This can be solved by:
However, this is used with the main act runner, however it is not propagated to the image used by container.
I can get it working by explicitly adding it to the container configuration inside the workflow, but then it breaks on GitHub that potentially cannot inject this SSL certificate.
I would also need to pass env variables
http_proxy
,https_proxy
andno_proxy
.Any idea if it is possible to pass options to these containers?
Beta Was this translation helpful? Give feedback.
All reactions