Skip to content

Fix link to related docs in the "Building best practices" manual #22469

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

Conversation

duffuniverse
Copy link
Contributor

Description

The pull request fixes the stale Celery documentation URL.

@github-actions github-actions bot added the area/build Relates to Dockerfiles or docker build command label Apr 22, 2025
Copy link

netlify bot commented Apr 22, 2025

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit dfa1152
🔍 Latest deploy log https://app.netlify.com/sites/docsdocker/deploys/6807a4ffb21add000800bcda
😎 Deploy Preview https://deploy-preview-22469--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -147,7 +147,7 @@ Limiting each container to one process is a good rule of thumb, but it's not a
hard and fast rule. For example, not only can containers be
[spawned with an init process](/manuals/engine/containers/multi-service_container.md),
some programs might spawn additional processes of their own accord. For
instance, [Celery](https://docs.celeryproject.org/) can spawn multiple worker
instance, [Celery](https://docs.celeryq.dev/) can spawn multiple worker
processes, and [Apache](https://httpd.apache.org/) can create one process per
request.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is another stale documentation URL in the Dockerfile instructions --> ENTRYPOINT section.

This script uses the exec Bash command so that the final running application becomes the container's PID 1.

Probably it could be substituted with a Linux manual page for the exec Bash command 💭

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

@crazy-max crazy-max left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@crazy-max crazy-max merged commit bdb512f into docker:main Apr 22, 2025
14 checks passed
@duffuniverse duffuniverse deleted the fix-links-to-docs-in-building-best-practices-manual branch April 22, 2025 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build Relates to Dockerfiles or docker build command
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants