Docker container fails to create the vikunja user #1392

New Issue

konrad · 2023-02-10T07:48:18Z

konrad commented

2023-02-10 07:48:18 +00:00

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

### 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_

konrad added the

kind/bug

label 2023-02-10 07:48:18 +00:00

konrad commented

2023-02-10 07:48:38 +00:00

@vlasov-y do you have an idea about this?

konrad commented

2023-02-11 08:01:06 +00:00

This seems to happen on try every time the database on try is reset. The cron which does that looks like this:

0 6 * * * /usr/bin/docker exec vikunja-try_db_1 sh -c 'mysql -uroot -pAighop0a vikunja < /demo/init.sql' && /usr/bin/docker restart vikunja-try_api_1

Still not sure why that would cause the container to fail restarting but it might be reproducible with restarting the container.

This seems to happen on try every time the database on try is reset. The cron which does that looks like this: ``` 0 6 * * * /usr/bin/docker exec vikunja-try_db_1 sh -c 'mysql -uroot -pAighop0a vikunja < /demo/init.sql' && /usr/bin/docker restart vikunja-try_api_1 ``` Still not sure why that would cause the container to fail restarting but it might be reproducible with restarting the container.

konrad referenced this issue from a commit

2023-02-15 09:39:52 +00:00

fix(docker): make sure the vikunja user always exists and only modify the uid instead of recreating the user

konrad closed this issue

2023-02-15 09:39:52 +00:00

konrad referenced this issue from a commit

2024-02-07 14:00:31 +00:00

chore(deps): update dependency vue-tsc to v0.30.5 (#1392)

Sign in to join this conversation.