I’m having some problems installing Vaultwarden and I wonder if it because I’m running docker compose in the wrong way and there are user permission issues.
What is the right way of installing docker compose (on a linux VM)? In in the past I would create a docker folder /home/user/docker. In there I would create the folder firefly or whatever and then I would run docker compose as user. So, when installing firefly, I would be in the /home/user/docker/firefly and run docker compose from within. Not as root (using sudo) but as a the normal user user. Firefly service would just run without problmes. Shoudl I be installing containers this way of shoudl I be using root (sudo)?
Yeah you can to that. I did this like you when I started with my homelab. I used podman very fast after playing with docker. You can just replace docker with podman ex:
podman pull x podman run x podman compose upPodman has better rootless support and is a bit more secure because of that.
Just a few tips (optional but I recommend you)
- Do not run container as root: If you run a container as root and the container gets hijacked someone could start/stop container on your behalf and since it would be possible to mount the root fs to the container they would be able to hijack the os. Do not mount the docker socked into the container unless you really trust the process and know the risks.
- UID/GID should not match with the hosts:
If you share the same UID (1000) from your
userand then the container has the same UID inside it, then they have technically the same permission set as your home directory or worse root directory (if UID is 0) and could do harm if they are exploited and can break free of the container - Remember to stay up to date: Go on Vaultwarden GitHub and subscribe to notifications about “Security” and “Releases”. Since I would use podman over docker you could have a look into podman auto updates feature.
- Limit container resources: Just do it. No downsides. Limit CPU and RAM usage of the container via the compose.yml file. If someone hacks the container they can’t mine bitcoin on it so easily and it chills your server abit. Here is how you can do that.
Kubernetes is a bit overkill and bloated for your usecase. Kubernetes would be interesting if you host a service with world wide access and millions of parralel users because of the nice scaling functionality of kubernetes.
What ever you do you did the right choice to learn something new, and I wish you fun and joy doing this! When I started vs today I learned many new things and practices which helped me earn money and have fun!
that is fine, the only requirement AFAIK is the user being in the docker group in case you’re having permission issues running it as user
Of course, i forgot to mention, that user is in the docker grp. I was just thinking that maybe, as the data folders/volumes for the containers were saved in the user home directory, there may be read/write issues foe the various containers.
Likewise, i was worried that if installing/running a sensitive service like Vaultwarden with sudo exposed me to risks.
Compose is just a single binary. There is no wrong way to install it really as long as it can find all the needed shared libraries and such.
If in doubt, look at the manual install instructions. Run through that, and see if it behaves any differently.
Some logs from the startup of a this container would help. Just run
docker compose up(without the -d) and you’ll get all the output up front.Or you know, move on to newer better tools that even docker uses internally instead of this limpdick unsupported tool.
Use kind, and kubernetes resources. You can literally use ‘kompose’ to convert your compose config, and then apply it to a local kind cluster.
