Comment

Comment on How to manage docker compose apps?

Docker compose pull; docker compose down;docker compose up -d

Pulls an update for the container, stops the container and then restarts it in the background. I’ve been told that you don’t need to bring it down, but I do it so that even if there isn’t an update, it still restarts the container.

You need to do it in each container’s folder, but it’s pretty easy to set an alias and just walk your running containers, or just script that process for each directory. If you’re smarter than I am, you could get the list from running containers (docker ps), but I didn’t name my service folders the same as the service name.

source

Sort:hotnew top

paequ2@lemmy.today ⁨1⁩ ⁨day⁩ ago
What commands do you have to run after you update docker-compose.yml or .env files? I updated one of those files once bad things happened… I haven’t had to update the configs in a long time.

source
- Passerby6497@lemmy.world ⁨1⁩ ⁨day⁩ ago
  I usually just do
  
  Docker compose down Docker compose up -d
  
  As I would with any service restart. The up -d command is supposed to reload it as well, but I prefer knowing for certain that the service restarted.
  
  Out of curiosity, what did you update and what broke? I had that happen a lot when I was first getting started with docker, and is part of how I learned. Once you have a basic template (or have dec supplies example files), it makes spinning up new services less of a hassle.
  
  Though I still get yelled at about the version entry in my fines because I haven’t touched mine in forever
  
  source
  - paequ2@lemmy.today ⁨1⁩ ⁨day⁩ ago
    My breakage happened a while ago, so I don’t quite remember all of the details…
    
    but what I think happened was I updated /etc/immich/.env. I updated the path for DB_DATA_LOCATION and/or UPLOAD_LOCATION and then I ran docker compose up -d I think. But nothing changed…
    
    source