github/dokku
0
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

fix: do not inject max-size option when not using local or json-file log drivers

Browse Source 
Closes #4376
This commit is contained in:
Jose Diaz-Gonzalez
2021-02-07 22:09:29 -05:00
parent f7beb3d95d
commit 065f5e5922
6 changed files with 88 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
docs/appendices/0.23.0-migration-guide.md
View File

@@ -5,3 +5,4 @@
- The `plugin:list` command no longer outputs the version for the `plugn` binary.
- Users building docker images that run Dokku will need to use a new sudoer wrapper for the `docker-image-labeler` binary to work correctly. A reference version has been placed in the `docker` skeleton directory. This should only impact platform developers, and users of our Docker image will already have the file available.
- The `dokku` user's cron is now in use by Dokku itself. Customizations will be overwritten. Users are encouraged to use a cron entry in `/etc/cron.d/dokku` to avoid this issue.
- As of 0.23.0, Dokku will now inject the `max-size` log driver option for applications. This is restricted to app-configured log driver values empty, `local` or `json-file` in 0.23.1 to increase setup compatibility. Users who configure alternative log drivers at the system level will need to either set the global `max-size` property to `unlimited` or switch to the built-in `vector` logging support.