Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dockerfile: Explictly create volume paths and set permissions #909

Merged
merged 1 commit into from
Jul 11, 2022

Commits on Jun 22, 2022

  1. Dockerfile: Explictly create volume paths and set permissions

    This allows running the docker image with a non-root user (--user 2000)
    with named/anonymous volumes (-v isso-db:/db).
    
    When an empty volume is mounted into a container (non-bind mount), it is
    prepopulated with the files at the mount path, including owners and
    permissions. The issue is that since /db does not exist at docker build
    time, the volume defaults to root ownership with 0755 permissions, which
    prevents non-root users from creating the sqlite database. This change
    explicitly creates the /config and /db directories with 1777 permissions
    to allow any user to write to them.
    
    Note that this has no impact on bind mounts, since these always use
    permissions of the host filesystem.
    mbrase committed Jun 22, 2022
    Configuration menu
    Copy the full SHA
    3597f5b View commit details
    Browse the repository at this point in the history