Portainer vs Compose and storage

So I’ve setup another pve. It hosts a VM of truenas scale and another VM for docker. Truenas SCale has 2 pools. One is a mirrored stripe (14/14, 18/18, 10/10 TB hdds). The other is 2 - 1TB mirrored ssds.

I didn’t want to bother with running docker in scale. I tried it, and it works, but just seemed like I should start off with a separate VM since truenas scale puts me in a crabby mood when I log into the web interface.

Currently all my active stuff is in LXC hosts on a different PVE. It works, I’m just trying something new to me.

Question 1 is this: do you use compose and git, or portainer and gui? From those that use docker, what works for you?

Question 2: do you store your containers on the docker VM’s disk and mount data from truenas, or do you go across the wire (10 gig) and store the containers on a zfs dataset?

I am in the process of moving from using Portainer to deploy stacks to using the command line and using docker compose and then only using Portainer for monitoring and also updating application versions. If there was a better way to visualize my Docker Swarm that the one in Portainer i would use that and ditch Portainer all together.

1 Like

I appreciate your feedback. I’m still not sure why I don’t leave it in LXC. I guess just to learn. Maybe I’ll try traefik instead of haproxy too. Maybe I’m just a glutton for punishment.