|
Minimsever update won't run
|
|
17-09-2025, 22:03
(This post was last modified: 18-09-2025 10:28 by simoncn.)
Post: #42
|
|||
|
|||
|
RE: Minimsever update won't run
I have found a way to extract debug information from a stopped or crashed container. From the command line, run this command:
Code: sudo docker commit <containername> <imagename>where <containername> is the name of the crashed container and <imagename> is the name of a new image to be created. The image name must be in all lower case. This creates a new image named <imagename> which contains the full contents of the crashed container. To retrieve and view the contents of this image, do the following: 1) Create a shared folder in DSM whose name is the image name. For example, if the image name is minimfiles, use minimfiles for the shared folder name. 2) Start a new container for the image by running this command: Code: sudo docker run -ti -v /volume1/minimfiles:/minimfiles --entrypoint=sh minimfilesThis starts a new container named minimfiles that has all the files from the crashed container. This new container maps the host volume /volume1/minimfiles to the directory /minimfiles in the new container (read/write). The new container is running an interactive shell and you can use shell comands to copy files from the crashed container to the host /volume1/minimfiles shared folder. 3) Use the interactive shell to copy files from the crashed container image to the host shared folder. For example, you can do this in the interactive shell: Code: cp -pr /opt/minimserver/data /minimfilesThis copies the full contents of the /opt/minimserver/data directory in the crashed container to the host /volume1/minimfiles shared folder. This doesn't require any changes to how the MinimServer container works and enables any information (logs, crash dumps, etc.) to be retrieved if the container crashes. |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



