Docker - Learnings

In between being a father and various other real-life requirements, I had dedicated this week to upgrading my Proxmox server to version 9 and after this was done, I turned my attention to my Portainer docker stacks that manage my lab and various experiments.

I came to a number of conclusions on this that I will share

1. I only have one hypervisor but technically could create others
2. With the deployment of a second of third node of the hypervisor and by connecting these nodes to the master existing node I could have used Portainer to transfer or duplicate the stacks I have deployed across the four docker servers I am running, in effect neutralizing the requirements of utilizing the backups.
3. However I made a blunder, I was using bind volumes. I have since changed this to docker volumes and can now move my stacks from one server to the other without loss of data.
4. It was a rather large oversight, but this now works rather well

I still have problems with ghost version 6.

1. I don't like Tinybird at all and have started to experiment with Google Analytics
2. I also don't like the way the Ghost 6 docker stack is deployed by ghost.org and since it is in preview I will have to wait till it moves into a more stable configuration. So, although this website is deployed using Ghost 6 all my internal ones will remain on Ghost version 5

Lots to learn with all of this. If I actually did this as my day job, obviously I would learn faster of have a colleague to discuss it with but at the moment it's just me.

I obviously need to spend more time in the ghost forums, which I will endeavor to do these 2 weeks why I am in remote Western Australia.

Anyhow, adjustments have been made and the whole lot can now be moved about as I see fit although I still need the base stacks to be deployed on each server prior to migrating or duplicating the stacks between servers.

#enoughsaid