LAB-linuxserver/cstate
1
0
Fork 0
mirror of https://github.com/linuxserver/cstate.git synced 2026-02-04 19:17:46 +08:00
Code Issues Packages Projects Releases Wiki Activity

Tweak wording

Browse Source
This commit is contained in:
TheSpad 2023-05-22 14:20:30 +01:00
parent 34211b898d
commit f571b802d3
No known key found for this signature in database
GPG Key ID: 08F06191F4587860
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -11,6 +11,6 @@ section: 'issue'
---
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 future, and there is not a practical or scalable solution that we can apply from our end to avoid this issue.
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.
**Our position remains that we provide support only for containers created and updated using Docker Compose or the Docker CLI, or using our Unraid templates, and not any 3rd party tools.**