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

Remove server.pid in the entrypoint if present #1556

Merged
merged 1 commit into from
Mar 8, 2025

Conversation

Oaphi
Copy link
Member

@Oaphi Oaphi commented Mar 8, 2025

closes #1555

If a uwsgi container is stopped with Rails running (for example, when using the out of the box Dockerfile), the /code/tmp/pids/server.pid file tracking the process id for the server is not cleaned up. If one then starts the container again without rebuilding, the server fails to start as the startup process thinks another instance is still running. At best, it's an inconvenience, at worst, it crashes the container.

@Oaphi Oaphi self-assigned this Mar 8, 2025
@Oaphi Oaphi requested a review from ArtOfCode- March 8, 2025 17:59
@Oaphi Oaphi added the area: deployment Changes to setting up QPixel, Docker, etc. label Mar 8, 2025
@ArtOfCode- ArtOfCode- merged commit b10d320 into develop Mar 8, 2025
9 checks passed
@ArtOfCode- ArtOfCode- deleted the 0valt/docker-fixes branch March 8, 2025 21:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: deployment Changes to setting up QPixel, Docker, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

server.pid file not removed when stopping docker containers
2 participants