Docker permissions issue

[aaronleopold]

Docker seems to create stump's config directory, on the host machine, with root privilege, making root the owner. This becomes a big problem during runtime, as stump won't have permissions to modify/access the config folder, which causes a ton of errors.

Changing the permissions manually fixes this, but this is really not ideal.

I have only been able to reproduce this issue on Linux (both a dedicated install, as well as WSL). Config folder must not already be present (~/.stump), otherwise issue won't occur.

[oliviacarino]

Hey! Just to clear things up, the goal is to give stump only the permissions to the config directory and not create it within the host machine?

Can I take on this issue?

[aaronleopold]

Hi! So to clarify, when the config folder (e.g. ~/.stump) does not exist on the host machine, Docker creates it with the root user as the owner. So if I had this compose file:

version: '3.3'
services:
  stump:
    image: aaronleopold/stump-preview
    ports:
      - '10801:10801'
    user: '1000:1000'
    volumes:
      - /Users/aaronleopold/Documents/Stump:/data
      - /Users/aaronleopold/.stump:/config

When I run docker compose up, docker creates /Users/aaronleopold/.stump with root and Stump internally throws a bunch of permissions errors, e.g. cannot create database or cannot create log file, etc. So the goal is to figure out how to get docker to create that config folder on the host machine not owned by root. Does that make sense?

If you still would like it, feel free to take it on! Keep in mind, if it is for hacktoberfest don't make the PR until it actually starts. Otherwise, I am not sure it will be counted towards your total.

For the quickest debugging, use a variation of pnpm build:docker-amd and not build:docker. The arm images take a long time 😄

[oliviacarino]

That makes sense, thank you :) I will still take it on!

[tuxuser]

That docker's standard behaviour and is not really fixable afaik.

The alternative would be to use a docker volume instead of a host-path-binding. Would that be an acceptable solution?

Update:

When trying to do the bind-mount, docker-compose actually errors out and won't let the user startup the container

# docker-compose up
Creating network "22_default" with the default driver
Creating stump ... error

ERROR: for stump  Cannot start service stump: Bind mount failed: '/volume2/docker/portainer/compose/22/config' does not exists

ERROR: for stump  Cannot start service stump: Bind mount failed: '/volume2/docker/portainer/compose/22/config' does not exists
ERROR: Encountered errors while bringing up the project.
# docker -v
Docker version 20.10.3, build 55f0773
# docker-compose -v
docker-compose version 1.28.5, build 24fb474e

[aaronleopold]

Resolved from #89