From 27b3db706df712a169e249edaaa30488a5ba00ed Mon Sep 17 00:00:00 2001 From: TheSpad Date: Sun, 21 May 2023 22:10:06 +0100 Subject: [PATCH] Portainer (& Synology) breaks things --- content/issues/2023-05-22-portainer.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 content/issues/2023-05-22-portainer.md diff --git a/content/issues/2023-05-22-portainer.md b/content/issues/2023-05-22-portainer.md new file mode 100644 index 00000000..83eb5658 --- /dev/null +++ b/content/issues/2023-05-22-portainer.md @@ -0,0 +1,16 @@ +--- +title: 'Known Issue: Portainer & Synology Docker UI' +date: '2023-05-22 12:00:00Z' +severity: notice +resolved: false +affected: + - 'Known Issues' + - 'portainer' + - 'synology' +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. + +**Our position remains that we provide support only for containers created and updated using Docker Compose or the Docker CLI, and not any 3rd party tools.**