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
Also, keep in mind that the docker group effectively grants root access.
The account can then mount any file or directory into a container and do whatever it wants.
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.
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.
Since when is docker compose unsupported?
I don't understand the question tbh. Make a docker-compose.yml in some folder, and then run your docker compose commands in that folder. Does that result in error and if so what errors?
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.