9
Running docker compose the right way (lemmy.ml)
submitted 3 weeks ago by trilobite@lemmy.ml to c/selfhost@lemmy.ml
7 comments fedilink hide all child comments

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)?

you are viewing a single comment's thread
view the rest of the comments
[-] trilobite@lemmy.ml 1 points 3 weeks ago

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.

this post was submitted on 20 Dec 2025
9 points (84.6% liked)

Self Hosted - Self-hosting your services.

17403 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules

Important

Cross-posting

If you see a rule-breaker please DM the mods!

founded 4 years ago
MODERATORS
dogmuffins@lemmy.ml
Zoe8338@lemmy.ml
testman@lemmy.ml