-
Notifications
You must be signed in to change notification settings - Fork 301
fix docker hosting example #2048
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
base: main
Are you sure you want to change the base?
Conversation
5e1bd90 to
b93887b
Compare
Fixes the following error message on `docker compose up`: > Error response from daemon: pull access denied for local, > repository does not exist or may require 'docker login': denied: > requested access to the resource is denied
b93887b to
a658af2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR fixes several issues in the Docker Compose example configuration within the hosting documentation. The changes correct service references, add missing components, and ensure the example configuration is complete and functional.
Key Changes:
- Added the missing
init-permservice for setting file permissions before initialization - Fixed the service dependency reference from
dbtodatabaseto match the actual service name - Added missing volume definitions that are referenced by services
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| entrypoint: > | ||
| chown 82:82 | ||
| /var/www/html/files | ||
| /var/www/html/public/theme | ||
| /var/www/html/public/media | ||
| /var/www/html/public/thumbnail | ||
| /var/www/html/public/sitemap |
Copilot
AI
Dec 18, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The entrypoint command using the YAML multiline string operator > will concatenate all lines into a single line with spaces. This means the command will become chown 82:82 /var/www/html/files /var/www/html/public/theme /var/www/html/public/media /var/www/html/public/thumbnail /var/www/html/public/sitemap which is incorrect syntax for the chown command. The -R flag is missing for recursive directory permissions, and the paths should be passed correctly. Consider using entrypoint: ["chown", "-R", "82:82", "/var/www/html/files", "/var/www/html/public/theme", "/var/www/html/public/media", "/var/www/html/public/thumbnail", "/var/www/html/public/sitemap"] or use a shell command with proper syntax.
| entrypoint: > | |
| chown 82:82 | |
| /var/www/html/files | |
| /var/www/html/public/theme | |
| /var/www/html/public/media | |
| /var/www/html/public/thumbnail | |
| /var/www/html/public/sitemap | |
| entrypoint: [ "chown", "-R", "82:82", "/var/www/html/files", "/var/www/html/public/theme", "/var/www/html/public/media", "/var/www/html/public/thumbnail", "/var/www/html/public/sitemap" ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-R was explicitly not added, because I want the initial startup using the example to work, but don't want to touch gigabytes of files each time I restart the container.
The other comment I do not get. What is wrong with the syntax? It works. Does it really need to be the very verbose array syntax? Why? Any links to official docs maybe?
Uh oh!
There was an error while loading. Please reload this page.