Docker container fails to create the vikunja user #1392
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1392
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Description
After a few random restarts (caused by watchtower or something else going wrong) the api docker container would fail to create the new vikunja Unix user with an error message like "failed to create user or group, already exists".
This is hard to reproduce, and I can't think of a reason why it would do that.
Maybe it's enough to not create the user when it already exists?
Vikunja Frontend Version
irrelevant
Vikunja API Version
current main
Browser and version
No response
Can you reproduce the bug on the Vikunja demo site?
Yes
Screenshots
No response
@vlasov-y do you have an idea about this?
This seems to happen on try every time the database on try is reset. The cron which does that looks like this:
Still not sure why that would cause the container to fail restarting but it might be reproducible with restarting the container.