LAB-linuxserver/cstate
1
0
Fork 0
mirror of https://github.com/linuxserver/cstate.git synced 2026-02-20 07:55:25 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #186 from linuxserver/resolve-portainer

Browse Source
This commit is contained in:
Roxedus 2023-11-22 15:30:08 +01:00 committed by GitHub
commit 4d7a7abe97
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
content/issues/2023-05-22-portainer.md
View File

@ -2,13 +2,20 @@
title: 'Known Issue: Portainer & Synology Docker UI'
date: '2023-05-22 12:00:00Z'
severity: notice
resolved: false
resolved: true
resolvedWhen: '2023-11-22 18:00:00Z'
affected:
- 'Known Issues'
- 'portainer'
- 'synology'
section: 'issue'
---
### Update
The underlying issue still exists for both Portainer and the Synology container management UI, but the primary driver of issues has largely dissipated and so we are unpinning this notice.
### Original Post
There is a known issue with Portainer and the Synology Docker UI when updating (or otherwise recreating) containers, which causes them to overwrite settings in the new image with values from the old container. Creating a new container from scratch does not exhibit this behaviour.
This non-standard behaviour causes containers to fail to start correctly in some cases, and may result in unexpected or unwanted configuration in others. For example, in our [SABnzbd image](https://github.com/linuxserver/docker-sabnzbd/issues/188) the `PATH` environment variable is overwritten, leaving the application unable to locate the necessary Python modules to enable it to start. This is likely to become more common in the future, and there is not a practical or scalable solution that we can apply from our end to avoid this issue.