When I start up my docker compose project all services quickly jump to the ‘status’ Started which seems normal (docker compose up -d --build). However I have one service which stays in Waiting forever.
However when I look at the output of docker ps it shows the service in the Up state (like all the others) and I can also look that the logs and they show what I expect.

I am attempting to take a working django production web app and containerize it. Every time it fails binding a port. When I check the port docker already owns it. When I do a sudo docker-compose down, the port is release. I am suspicious it is in my compose file as I use nginx and uwsgi. Here is my yml file:

After i run docker-compose up or docker-compose build i get error with python packages.
I want my docker and docker compose to be independent from python.
I am using kubuntu

how do you handle an error of docker compose build that basically just shows you the error code below: ime=”2024-07-29T16:56:29+01:00″ level=warning msg=”The “AIRFLOW_UID” variable is not set. Defaulting to a blank string.” time=”2024-07-

My goal is simple – it is to create a script that sets up my local environment before tests are ran, and logs of my containers are vital to that – sometimes, due to some env changes, the startup fails and I need to see immediately what went wrong.

I’m having the issue that Docker containers don’t get an IPv6 address assigned and therefore are unable to connect to IPv6-only hosts.

tudo bem?

docker-compose entrypoint tag escaping single quotes not working..
I tried the code to escape single quotes in docker-docker entrypoint tag. This works from my command line but doesn’t work from docker-compose entrypoint…

I followed this tutorial from the OVH site Installing WordPress with Docker on a VPS.

I have two development environments that regularly run projects that use docker-compose. I always gracefully stop the docker-compose process before shutting down the system. One laptop has suddenly begun automatically starting a particular container under a particular docker-compose configuration at boot-up. The other system starts like ten containers (a couple of containers in like five different docker-compose configurations), and has been doing this for a year.