Page 2 of 2
Re: Docker config gone after update
Posted: 24 Mar 2023, 20:06
by XFNeo
Have you fixed this issue?
Re: Docker config gone after update
Posted: 21 Apr 2023, 20:53
by XFNeo
Is the issue fixed in TOS 5.1.31 ?
Re: Docker config gone after update
Posted: 04 May 2023, 16:00
by MooieBoot
Or docker update or TOS update made my connected folders readonly.
That's what the app says, but they're all empty/inaccessible.
Had to re-assign folders for all docker instances.....
Re: Docker config gone after update
Posted: 04 May 2023, 19:29
by TMzethar
This issue is still being fixed. May I ask if the network configuration of the error container you used before is all "HOST"?
Re: Docker config gone after update
Posted: 03 Aug 2023, 00:02
by davidecavestro
Guys, I just noticed that upgrading the Docker manager app (which in turn seems to deploy containerd and the whole docker stuff)
the daemon.json configuration used by the daemon and hosted at path /Volume1/@apps/docker/conf/daemon.json
is simply overwritter
so that any customization applied there - such as dns, logging opts - gets lost
ahem... Is this wanted?
TOS 5.1.40
Docker manager 1.2.2
Re: Docker config gone after update
Posted: 03 Aug 2023, 19:23
by TMzethar
This file has nothing to do with Docker and container configuration.
You can find configuration files in /Volume1/DockerData/containers/container id.
Re: Docker config gone after update
Posted: 05 Aug 2023, 13:45
by davidecavestro
TMzethar wrote: ↑03 Aug 2023, 19:23
This file has nothing to do with Docker and container configuration.
I'm sorry to disagree.
When I run
I get
Code: Select all
11898 /Volume1/@apps/docker/dockerd/bin/dockerd --config-file=/Volume1/@apps/docker/conf/daemon.json
So at path
/Volume1/@apps/docker/conf/daemon.json there's the config with params for the docker daemon.
GIven that docker advanced users sometimes need to customize it (i.e. to set custom DNS or change the IP address range to avoid conflicts, or change the logging driver for better performance, etc).
My point is that
packaging this file along with the app implies loosing any customization at every upgrade.
Am I wrong?
TMzethar wrote: ↑03 Aug 2023, 19:23
You can find configuration files in /Volume1/DockerData/containers/container id.
I agree that
/Volume1/DockerData/containers/container id is the path where docker by default stores the state/config of each specific container, such as the resolv.conf previously mentioned.
It's not my point in this case.
Re: Docker config gone after update
Posted: 13 Aug 2023, 20:38
by davidecavestro
TMzethar wrote: ↑03 Aug 2023, 19:23
This file has nothing to do with Docker and container configuration.
You can find configuration files in /Volume1/DockerData/containers/container id.
Again...
about
/Volume1/@apps/docker/conf/daemon.json:
packaging this file along with the docker distribution implies loosing any customization at every upgrade.
Am I wrong?
Re: Docker config gone after update
Posted: 14 Aug 2023, 19:10
by TMzethar
davidecavestro wrote: ↑13 Aug 2023, 20:38
Again...
about
/Volume1/@apps/docker/conf/daemon.json:
packaging this file along with the docker distribution implies loosing any customization at every upgrade.
Am I wrong?
This is the setting for the Docker app. After updating, it will be overwritten by the default configuration. It is not recommended that you modify it. If you insist, you may need to backup and modify it frequently.
Re: Docker config gone after update
Posted: 15 Aug 2023, 16:17
by davidecavestro
TMzethar wrote: ↑14 Aug 2023, 19:10
davidecavestro wrote: ↑13 Aug 2023, 20:38
Again...
about
/Volume1/@apps/docker/conf/daemon.json:
packaging this file along with the docker distribution implies loosing any customization at every upgrade.
Am I wrong?
This is the setting for the Docker app. After updating, it will be overwritten by the default configuration. It is not recommended that you modify it. If you insist, you may need to backup and modify it frequently.
I see... so I assume the only option to control logs for the whole docker daemon is setting the Log Retention through Docker Manager user interface. Then any customized log option (i.e. changing
the driver) should be set on a per-container basis.