Execution containers do not respect tentacle proxy configuration

[IsaacCalligeros95]

Severity

Low, workarounds available

Version

All, Latest

Latest Version

I could reproduce the problem in the latest build

What happened?

When running steps within an execution container the worker or deployment targets tentacle proxy configuration is not used, the default is instead.

Reproduction

• Configure a Tentacle with a proxy configuration
  • Host: host.docker.internal
  • Port: 3128
• Configure a proxy service
  • To use Squid proxy run docker pull ubuntu/squid:5.2-22.04_beta and docker run -d --name squid-container -e TZ=UTC -p 3128:3128 ubuntu/squid:5.2-22.04_beta
• Run a deployment that makes an external call, squid proxy logs will not reflect this call being made

Error and Stacktrace

No response

More Information

No response

Workaround

• Run directly on the worker
• Configure docker to use a proxy - see https://docs.docker.com/network/proxy/#configure-the-docker-client

[michelle-luana]

The Octopus engineering team has reviewed this issue.
After careful consideration, we’ve classed this low priority. This means we won’t work on it in the near future. We prioritize issues based on the number of people affected, the impact type, and available workarounds. If you’ve encountered this issue and haven’t informed our support team, please email support@octopus.com. Knowing how many people this issue affects helps us determine its priority.