Your compose file will pull the image when you run it, from the registry it's in
on that update train right now
I have all external mounts in /mnt
, if my container needs to use it then it's in the compose file to use the local mount.
All my compose and stacks are in a git repo, the repo lives in my home dir and pulled fromy Gogs server. That only I can access.
can we all chip in and get one sent to Trump as a welcome gift?
can confirm nextcloud news alpha is great, as is the mobile app
Thats how I had my setup run, point the volume at NFS
If you have your services in compose files, you can point the volumes to anywhere. Even NFS.
Like the below config
volumes:
pihole01:
driver: local
driver_opts:
type: 'none'
o: 'bind'
device: '/mnt/data/docker/pihole01'
I think you can make a template from the helpers page, see if that works
I leave my servers running 24/7, thats the point of a server. Also my home automation would be a little pointless if its off.
I did have a UPS, but it died and I have got round to replacing it.
Its all horses for courses, if your homelab is a playground to test things out then turning it off when not is use is fine. But some have live services that you may want at a moments notice and there for having it up all the time is better.
me remembering I caused an outage yesterday by deleting nginx config 🤦♂️
that looks to be almost all steaming services adding an ad-supported option, you now pay to not have ads.
Back to the high sea's to watch anything then
I would start with a Debian os base, install docker and turn it into a swarm manager. Then look at stacks and how services work, if you find your running your host too hard. You can add a work host and stread out.
Once you have docker swarm running, get portainer running. I use portainer as a visual
whats happening
on my swarm, but I use the docker cli to start and update all my stacks. I have my stacks in a git repository so that I have a backup and history of what changes I did.Now your a docker master, of sorts.