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

[GH-ISSUE #1233] Account messing up in Docker build #6340

New Issue
Closed
opened 2026-04-20 16:55:38 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-20 16:55:38 -05:00
Owner
Copy Link

Originally created by @boxsnake on GitHub (Aug 4, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1233

Description

In Docker build, I created the first user (user X) in Computer A. And then create second user (user Y) in Computer B.

After refreshing in Computer A, I am logged in user X even though I have not logged in with user Y in Computer A.

Docker compose .yaml

networks:
  vikunja:
    external: false
services:
  vikunja:
    image: vikunja/vikunja
    container_name: ${PREFIX}vikunja
    restart: always
    environment:
      VIKUNJA_SERVICE_PUBLICURL: ${VIKUNJA_URL}
      VIKUNJA_DATABASE_HOST: mariadb
      VIKUNJA_DATABASE_PASSWORD: vikunja
      VIKUNJA_DATABASE_TYPE: mysql
      VIKUNJA_DATABASE_USER: vikunja
      VIKUNJA_DATABASE_DATABASE: vikunja
      VIKUNJA_SERVICE_JWTSECRET: ${VIKUNJA_JWT_SECRET}
    ports:
      - ${VIKUNJA_PORT:-7456}:3456
    networks:
      - vikunja
    volumes:
      - ${DATA_DIR:-./data}/vikunja/files:/app/vikunja/files
    depends_on:
      - mariadb
  mariadb:
    image: mariadb:10
    container_name: ${PREFIX}mysql
    restart: always
    command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
    environment:
      - MYSQL_ROOT_PASSWORD=vikunja
      - MYSQL_USER=vikunja
      - MYSQL_PASSWORD=vikunja
      - MYSQL_DATABASE=vikunja
    networks:
      - vikunja
    volumes:
      - ${DATA_DIR:-./data}/mariadb:/var/lib/mysql

Vikunja Version

latest

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Please select

Screenshots

No response

Originally created by @boxsnake on GitHub (Aug 4, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1233 ### Description In Docker build, I created the first user (user X) in Computer A. And then create second user (user Y) in Computer B. After refreshing in Computer A, I am logged in user X even though I have not logged in with user Y in Computer A. Docker compose .yaml ``` yaml networks: vikunja: external: false services: vikunja: image: vikunja/vikunja container_name: ${PREFIX}vikunja restart: always environment: VIKUNJA_SERVICE_PUBLICURL: ${VIKUNJA_URL} VIKUNJA_DATABASE_HOST: mariadb VIKUNJA_DATABASE_PASSWORD: vikunja VIKUNJA_DATABASE_TYPE: mysql VIKUNJA_DATABASE_USER: vikunja VIKUNJA_DATABASE_DATABASE: vikunja VIKUNJA_SERVICE_JWTSECRET: ${VIKUNJA_JWT_SECRET} ports: - ${VIKUNJA_PORT:-7456}:3456 networks: - vikunja volumes: - ${DATA_DIR:-./data}/vikunja/files:/app/vikunja/files depends_on: - mariadb mariadb: image: mariadb:10 container_name: ${PREFIX}mysql restart: always command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci environment: - MYSQL_ROOT_PASSWORD=vikunja - MYSQL_USER=vikunja - MYSQL_PASSWORD=vikunja - MYSQL_DATABASE=vikunja networks: - vikunja volumes: - ${DATA_DIR:-./data}/mariadb:/var/lib/mysql ``` ### Vikunja Version latest ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Please select ### Screenshots _No response_
GiteaMirror added the waiting for reply label 2026-04-20 16:55:38 -05:00
GiteaMirror commented 2026-04-20 16:55:40 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 4, 2025):

And you can verify both users exist?

<!-- gh-comment-id:3150521059 --> @kolaente commented on GitHub (Aug 4, 2025): And you can verify both users exist?
GiteaMirror commented 2026-04-20 16:55:42 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 31, 2025):

Closing as inactive, please ping or open a new issue with relevant information if you still have this problem.

<!-- gh-comment-id:3240365604 --> @kolaente commented on GitHub (Aug 31, 2025): Closing as inactive, please ping or open a new issue with relevant information if you still have this problem.
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 Label waiting for reply
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6340
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?