docker-ce | : warning : This repository is deprecated and will be | Continuous Deployment library

The reason for the website becoming unreachable is that WSL2 only binds ports to the localhost and not to every interface.
Docker desktop itself binds to every interface and forwards everything to WSL2 that is why it worked. For docker-ce a manual solution is required.
The problem is documented in the wsl documentation and a solution is described.
A script for discovering and setting the port forwarding automatically is found in an older WSL2 issue on github.

With the localhostForwarding option set (documentation) for WSL2 the following commands work too:

netsh interface portproxy add v4tov4 listenport=80 connectport=80 connectaddress=127.0.0.1
netsh interface portproxy add v4tov4 listenport=443 connectport=443 connectaddress=127.0.0.1

In some future version Microsoft may bring the bridged networking option back for WSL2 see issue discussion.

When you run foo=mandatory docker-compose up && docker-compose down, you are running foo=mandatory docker-compose up and then docker-compose down, which means the docker-compose down is not receiving that variable, and thus giving you that error when trying to read the template.

If you run foo=mandatory docker-compose up && foo=mandatory docker-compose down, it will work. You may also export the variable so you don't need to pass it twice:

I was able to resolve this, unfortunately I won't be able to find out why this happened.

I tried removing and installing docker-ce and dependencies again. I wasn't able to remove due to containerd.service not stopping. I found it was set to always restart, which would normally make sense. I then ran sudo systemctl disable docker containerd and rebooted. I confirmed those services were no longer running by following journalctl output, looking for the usual restarting and core-dump errors from docker and containerd.

I ran sudo apt remove docker-ce and sudo apt autoremove again, then ran docker's get-docker.sh which reinstalled docker. I then ran sudo systemctl enable docker containerd and sudo systemctl start docker containerd. Docker is the same version it was before and the hello-world container and other containers of mine that wasn't previously running is now running successfully.

Executing the command with sudo fixes the issue as a workaround.

Executing the run-command without sudo after a dockerd-rootless-setuptool.sh installation causes the stated issue where the network interfaces are not available, instead a virtual interface is created.

Turns out that the docker and docker-compose binaries were irrelevant, I had to update the docker CLI by running sudo curl -L https://raw.githubusercontent.com/docker/compose-cli/main/scripts/install/install_linux.sh | sudo sh. The new workflow looks like this:

Try to use --network jenkins while building sonarqube container.

Or donot use --network parameter, its default to use bridge mode for both containers

Jenkins and Sonarqube should be the same network. Then try to use http://172.17.0.1:9000 or http://sonarqube:9000 if http://localhost:9000 does not work.

The issue seemed to be the number of times I had requested a certificate for those specific domains. I tried the deploy multiple times to figure out how to do it properly for the deployment server and also to write a proper version of the script, that I requested many times a certificate for two specific domains.

The issue was resolved after I tried a different domain and subdomain.

It looks like you trying to run the docker daemon inside your build image docker run.

For Linux, you need to make sure that the current user (the one running sbt), has the proper permissions to run docker commands with some post-install steps.

Maybe you could fix your script by running sudo sbt docker:publishLocal instead?

It is more common now to use a service to have a docker daemon already set up for your builds:

Error is from AWS cli it's have permission

you should run