Dutch software engineer, supporter of N.E.C. !nec@ymmel.nl

  • 8 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle








  • So there’s a million ways to do things and what works for you works for you. For me, putting all services ina single compose file only has downsides.

    • Difficult to search, I guess searching for a name and then just editing the file works - but doesn’t it become a mess fairly quickly? I sometimes struggle with just a regular yaml file lmao
    • ^also missing an overview of what you’re exactly running - docker ps -a or ctop or whatever works - but with an ls -la I clearly see whats on my system
    • How do you update containers? I use a ‘docker compose pull’ to update the images which are tagged with latest.
    • I use volume mounts for config and data. A config dir inside the container is mounted like ‘./config:/app/data/config’ - works pretty neatly if each compose file is in its own named directory
    • Turning services on/off is just going into the directory and saying docker compose up -d / or down - in a huge compose file don’t you have to comment the service out or something?








  • Can you reach file browser regularly? Attach it to a bridge network and expose the correct port to see if the container is running properly. Or check the docker logs for it. Could be that the reverse proxying isn’t working but I’d check the actual container first and go from there.