From 27b3db706df712a169e249edaaa30488a5ba00ed Mon Sep 17 00:00:00 2001 From: TheSpad Date: Sun, 21 May 2023 22:10:06 +0100 Subject: [PATCH 1/4] 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.** From 34211b898d53f506ac423a460ac64c10a6c122df Mon Sep 17 00:00:00 2001 From: TheSpad Date: Sun, 21 May 2023 22:17:59 +0100 Subject: [PATCH 2/4] Add unraid note --- content/issues/2023-05-22-portainer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/issues/2023-05-22-portainer.md b/content/issues/2023-05-22-portainer.md index 83eb5658..bcf285f9 100644 --- a/content/issues/2023-05-22-portainer.md +++ b/content/issues/2023-05-22-portainer.md @@ -13,4 +13,4 @@ There is a known issue with Portainer and the Synology Docker UI when updating ( 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.** +**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.** From f571b802d3fe9e54d2ebb18fc9c1e2ac693fe588 Mon Sep 17 00:00:00 2001 From: TheSpad Date: Mon, 22 May 2023 14:20:30 +0100 Subject: [PATCH 3/4] Tweak wording --- content/issues/2023-05-22-portainer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/issues/2023-05-22-portainer.md b/content/issues/2023-05-22-portainer.md index bcf285f9..e4fe9275 100644 --- a/content/issues/2023-05-22-portainer.md +++ b/content/issues/2023-05-22-portainer.md @@ -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.** From 794166a49802a3d1dabe61b15ede484f12df14ca Mon Sep 17 00:00:00 2001 From: TheSpad Date: Mon, 22 May 2023 14:22:54 +0100 Subject: [PATCH 4/4] More grammars --- content/issues/2023-05-22-portainer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/issues/2023-05-22-portainer.md b/content/issues/2023-05-22-portainer.md index e4fe9275..3582341b 100644 --- a/content/issues/2023-05-22-portainer.md +++ b/content/issues/2023-05-22-portainer.md @@ -13,4 +13,4 @@ There is a known issue with Portainer and the Synology Docker UI when updating ( 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.** +**Our position remains that we provide support only for containers created and updated using Docker Compose, the Docker CLI, or using our Unraid templates, and not any 3rd party tools.**