After migration to FDO, TFE is using old Replicated proxy configuration – HashiCorp Help Center

Problem

After migration to FDO, TFE is using the proxy configuration that was not specified in the Docker Compose file. (e.g. http_proxy, https_proxyand/or no_proxy)

Prerequisites

TFE FDO is installed on the same Docker host(s) as Replicated.

Cause

This configuration is present on Docker daemon level and TFE FDO container is inheriting it.

To validate this, you can execute docker ps, copy the Container ID of the FDO image (typically, images.releases.hashicorp.com/hashicorp/terraform-enterprise:vXXXX-YY) and use docker inspect <Container_ID> to check what is being injected into the container.

Solution

SSH into the TFE instance and run find /etc/docker
Inspect any file listed there. Additionally, check the ~/.docker/config.json file and home directory for root: /root/.docker/config.json
When it's done and corrections have been made, restart the Docker service to pick up the changes.

To restart services manually, follow the steps below:

Switch to a folder with Docker Compose file
```
cd /path_docker_compose_file
```
Stop service
```
docker compose down
```
Start service
```
docker compose up --detach
```

If you configured Systemd service, run

systemctl restart terraform-enterprise.service

Outcome

Once the configuration has been corrected, TFE FDO container will only use the configuration specified in the Docker Compose file.

Additional Information