github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-08-03 09:06:10 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Using a custom puid:guid with docker doesn't work #1855

New Issue
Closed
opened 2026-03-22 13:42:04 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-03-22 13:42:04 -05:00
Owner
Copy Link
Copy Source

Originally created by @marouamghar on GitHub (Mar 19, 2023).

Description

Wen specifying the puid:guid with the user field with docker, both the api and the frontend don't deploy
The api starts failing with the error :
groupmod: /etc/group.8: Permission denied
The frontend fails with the error :
sed: can't create temp file '/usr/share/nginx/html/index.htmlXXXXXX': Permission denied

Vikunja Frontend Version

latest

Vikunja API Version

latest

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @marouamghar on GitHub (Mar 19, 2023). ### Description Wen specifying the puid:guid with the user field with docker, both the api and the frontend don't deploy The api starts failing with the error : `groupmod: /etc/group.8: Permission denied` The frontend fails with the error : `sed: can't create temp file '/usr/share/nginx/html/index.htmlXXXXXX': Permission denied` ### Vikunja Frontend Version latest ### Vikunja API Version latest ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-03-22 13:42:05 -05:00
Author
Owner
Copy Link
Copy Source

@kolaente commented on GitHub (Mar 20, 2023):

Can you share the full command you used?

@kolaente commented on GitHub (Mar 20, 2023): Can you share the full command you used?
GiteaMirror commented 2026-03-22 13:42:06 -05:00
Author
Owner
Copy Link
Copy Source

@marouamghar commented on GitHub (Mar 20, 2023):

  vikunja_db:
    container_name: vikunja_db
    image: postgres
    restart: always
    user: ${PUID}:${PGID} 
    volumes:
      - ${ROOT_DOCKER}/vikunja/postgres/data:/var/lib/postgresql/data
    environment:
      - POSTGRES_DB=vikunja
      - POSTGRES_USER=user
      - POSTGRES_PASSWORD=password

  vikunja_api:
    container_name: vikunja_api
    image: vikunja/api
    user: ${PUID}:${PGID} 
    environment:
      VIKUNJA_DATABASE_TYPE: postgres
      VIKUNJA_DATABASE_HOST: vikunja_db
      VIKUNJA_DATABASE_PASSWORD: password
      VIKUNJA_DATABASE_USER: user
      VIKUNJA_DATABASE_DATABASE: vikunja
      VIKUNJA_SERVICE_JWTSECRET: secret
    volumes: 
      - ${ROOT_DOCKER}/vikunja/files:/app/vikunja/files
    depends_on:
      - vikunja_db
    restart: unless-stopped

  vikunja_frontend:
    container_name: vikunja_frontend
    image: vikunja/frontend
    user: ${PUID}:${PGID} 
    restart: unless-stopped
@marouamghar commented on GitHub (Mar 20, 2023): ``` vikunja_db: container_name: vikunja_db image: postgres restart: always user: ${PUID}:${PGID} volumes: - ${ROOT_DOCKER}/vikunja/postgres/data:/var/lib/postgresql/data environment: - POSTGRES_DB=vikunja - POSTGRES_USER=user - POSTGRES_PASSWORD=password vikunja_api: container_name: vikunja_api image: vikunja/api user: ${PUID}:${PGID} environment: VIKUNJA_DATABASE_TYPE: postgres VIKUNJA_DATABASE_HOST: vikunja_db VIKUNJA_DATABASE_PASSWORD: password VIKUNJA_DATABASE_USER: user VIKUNJA_DATABASE_DATABASE: vikunja VIKUNJA_SERVICE_JWTSECRET: secret volumes: - ${ROOT_DOCKER}/vikunja/files:/app/vikunja/files depends_on: - vikunja_db restart: unless-stopped vikunja_frontend: container_name: vikunja_frontend image: vikunja/frontend user: ${PUID}:${PGID} restart: unless-stopped ```
GiteaMirror commented 2026-03-22 13:42:07 -05:00
Author
Owner
Copy Link
Copy Source

@kolaente commented on GitHub (Mar 20, 2023):

That won't work because Vikunja starts as root, changes the permissions and then drops its privileges. You can use the PUID and PGID env variables to change the uid and gid of the user running Vikunja, as documented here.

The frontend container does not support changing the user id as it runs as an unprivileged user and does not expose anything (volumes etc) to the host which would require different permissions.

@kolaente commented on GitHub (Mar 20, 2023): That won't work because Vikunja starts as root, changes the permissions and then drops its privileges. You can use the `PUID` and `PGID` env variables to change the uid and gid of the user running Vikunja, as documented [here](https://vikunja.io/docs/install-backend/#setting-user-and-group-id-of-the-user-running-vikunja). The frontend container does not support changing the user id as it runs as an unprivileged user and does not expose anything (volumes etc) to the host which would require different permissions.
GiteaMirror commented 2026-03-22 13:42:07 -05:00
Author
Owner
Copy Link
Copy Source

@marouamghar commented on GitHub (Mar 20, 2023):

That won't work because Vikunja starts as root, changes the permissions and then drops its privileges. You can use the PUID and PGID env variables to change the uid and gid of the user running Vikunja, as documented here.

The frontend container does not support changing the user id as it runs as an unprivileged user and does not expose anything (volumes etc) to the host which would require different permissions.

Thanks for the link, I missed it.
For the frontend container, yeah I arrived to that conclusion and didn't post the same issue on the other repo, but forgot to clean it here.

@marouamghar commented on GitHub (Mar 20, 2023): > That won't work because Vikunja starts as root, changes the permissions and then drops its privileges. You can use the `PUID` and `PGID` env variables to change the uid and gid of the user running Vikunja, as documented [here](https://vikunja.io/docs/install-backend/#setting-user-and-group-id-of-the-user-running-vikunja). > > The frontend container does not support changing the user id as it runs as an unprivileged user and does not expose anything (volumes etc) to the host which would require different permissions. Thanks for the link, I missed it. For the frontend container, yeah I arrived to that conclusion and didn't post the same issue on the other repo, but forgot to clean it here.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#1855