wait-for-it VS podman-compose

python:3.10.5-slim-buster is a Debian GNU/Linux 10 (buster). Follow the Debian package link given by wait-for-it, we'll eventually find this link https://packages.debian.org/source/oldoldstable/wait-for-it, I downloaded the wait-for-it_0.0~git20160501.orig.tar.gz file and extracted wait-for-it.sh out to the project root directory where setup.py, app.py, .dockerignore, Dockerfile and docker-compose.yml are.

Using countless variations of the wait for it script (they all get ignored (yes i did chmod +x)). another candidate or using it like this

I haven’t done it, but maybe you can use something like this in an ExecStartPre on the nginx systemd service, or if that doesnt work, as a separate service that nginx’s systemd service starts after

I’ve used wait-for-it with success.

https://github.com/vishnubob/wait-for-it

When start to build docker-compose, it tried to connect db first, but it seems that db didn't become reachable yet. Even added wait-for-it doesn't work.

executes 'wait-for-it.sh' to wait on the availability of port 3306 before running 'air'--using wait-for-it.sh is just an example and this shell script has to be installed as part of the Dockerfilehttps://github.com/vishnubob/wait-for-it

Yeah dockerize seems to achieve your second suggestion, someone also suggested my wait-for-it https://github.com/vishnubob/wait-for-it which seems to be similar but a bit more popular and also used in the official documentation https://docs.docker.com/compose/startup-order/ I think I'll go this route, the first option doesn't quite match what I need as all compose aren't necessarily to be started simultaneously.

Can't you use something like this? : https://github.com/vishnubob/wait-for-it . Essentially wait until you can ping redis port and then run wsgi runserver for django. However, are you sure that you can resolve redis host on swarm? Redis starts so fast that it makes me think it might be something else.

Podman (via podman-compose),

Source code for the feature is here if you care to inspect it:

https://github.com/containers/podman-compose/blob/bce40c2db3...

Admittedly, I'm still on podman 4.3.1, but I dont' see any reason why this would stop working in later versions of podman.

Can someone link me to what Compose means in this context? Google takes me to https://github.com/containers/podman-compose but I just wanna make sure that's what they are talking about.

🛑 Docker Desktop is free for personal use but requires a paid subscription for enterprises. A free open source alternative is Podman and Podman Compose which uses the same core syntax as the Docker tools and can be used as a near drop-in replacement.

I’m dumb. When I wrote the article it was late. Docker-Compose really was a game changer.

Yea Podman compose exists. I’ll add a section about docker compose to it in an update.

https://github.com/containers/podman-compose

From googling this error I've come across a few different threads but I haven't gained any success. Firstly I found this github thread which doesn't reference my error but still seems related. I followed the "sudo podman-compose systemd --action create-unit" and "podman-compose systemd -a register -f myfile.yml" minus the -f flag as it wouldnt run with that. This indeed created a [email protected] file, but its created in the /etc/systemd/user directory rather than /etc/systemd/system which raises an issue as I'm having to run these two containers as root. I try registering the podman-compose@torrent but I'm told the service doesnt exist. Running it as user I'm told it failed to connect to bus: no medium found. So I basically reached a dead end there.

Have a look at Podman Compose

You can also use podman-compose for the orchestration https://github.com/containers/podman-compose