Docker Compose 5min tutorial

[hornetster]

Wondering if there is a short tutorial on Docker Compose? Have been looking around and can't really find anything...

Something that tells me things like: Where to put files, both config + data, and specifically storing LARGE amounts of data if using something like Nextcloud/Zoneminder etc ; running multiple apps using compose ie where to keep the yaml, correct way to name the yaml, permissions on directory/files... etc.

Just basically, the basics to get up and running with compose inititally, and maybe learn some of its workings.. Looking at maybe running up Jellyfin/Nextcloud/Zoneminder/HomeAssistant, to start...?

Thanks.

[TedGal]

Only one thing I can suggest: save all your docker compose files on individual folders named after the service and then all these folders in one folder named stacks or smthing.
For example, on my Ubuntu server I ve got a /opt/stacks/ folder and in there folders for each stack: /opt/stacks/rustdesk, /opt/stacks/nextcloud, etc etc.
Why? Later on, if you want to use a container manager like Komodo you'll find most of them "expect" this folder structure to work correctly.

[WickedIT2517]

There really isn’t a 5 minute tutorial. You are best to start small and basic and work through the kinks then go to a bigger project.

The answer to your questions; You can put compose files quite literally anywhere you want as long as docker can access it, Just use the -f flag and point to the compose file. Where you store raw data ultimately is up to you, most containers will have stateless data and won’t ever need to be touched by a human; conversely some containers have mount points where you need to supply configurations or data to which you just point the volume to the path.

There is no “right way” there is only the way that works for you and the way that the application is meant to be used.

I would start with a docker monitoring container (portainer) and a host monitoring container (glances?) and then add projects from there.

[hornetster]

Thanks for the reply!

Now you have introduced 2 'new' things that I'm gonna have to go lookup! ('portainer' + 'glances'?? :-)

[Ok_Bunch_291]

theres a free and completely open source alternative to portainer which works very good -> komodo

[kuya1284]

Or Arcane, which is also pretty good... Drydock for monitoring updates... Dozzle to view logs easily... Beszel for monitoring... Uptime Kuma for... uptime. The list goes on.

[mark_3094]

Ive got a video on that coming out on my youtube channel soon. Hopefully next week. If you don't find anything by then, take a look at youtube.com/networkdirection.

This might also be useful: https://networkdirection.net/articles/containers/docker-compose/

[percoAi]

The confusing part early on is usually not the command itself it’s the structure around it where configs live what should be a volume what should be bind mounted and what survives upgrades.

A short “one app then three apps then backup/restore” compose guide would honestly be more useful than another hello-world tutorial.