refactor: simplify file ownership in the container by setting the process ownership during the build process
Rather than require a heavy chown operation across various paths, just chown the files already in the built image during the release process. This ensures we can skip not-only the chown process during the container start that herokuish injects, but also the one that Dokku runs which modifies mounted container paths as well during the pre-deploy. Note that users will need to ensure any mounted volumes don't have permissions reset by other processes or containers won't be able to access them.
This commit is contained in:
5
docs/appendices/0.34.0-migration-guide.md
Normal file
5
docs/appendices/0.34.0-migration-guide.md
Normal file
@@ -0,0 +1,5 @@
|
||||
# 0.34.0 Migration Guide
|
||||
|
||||
## Removals
|
||||
|
||||
- The `disable-chown` property of the `scheduler-docker-local` plugin has been removed. Mounted paths will no longer have file permissions changed during the pre-deploy phase. Files baked into the container image for herokuish builds will always be owned by the correct user.
|
||||
Reference in New Issue
Block a user