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

Startup fails when reusing the container #21

Open
ih84ds opened this issue Mar 16, 2018 · 0 comments
Open

Startup fails when reusing the container #21

ih84ds opened this issue Mar 16, 2018 · 0 comments

Comments

@ih84ds
Copy link

ih84ds commented Mar 16, 2018

When restarting an existing container, the entrypoint script attempts to recreate afpuser even if it already exists:

groupadd: group 'afpuser' already exists
adduser: The user `afpuser' already exists.

Also, the netatalk daemon exits immediately upon startup with a cryptic error message. It's possible that this is related to the above error, or it could be a totally separate problem.

netatalk is already running (pid = 1), or the lock file is stale.
exited with code 3

To reproduce, simply stop and start the container a few times. I am running via docker-compose, but I don't think that matters.

ih84ds added a commit to ih84ds/docker-netatalk that referenced this issue Mar 16, 2018
Ensure lockfile does not exist before startup. This works around issue cptactionhank#21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant