I have a support application, SimpleHelp, that I am running in a Docker Container in Container Station. It works great except I have one problem. I am not able to update the SimpleHelp software as new releases come out. Sure, I could create a new container but that is tedious doing that every time and recreating all my preferences, etc.
What I want to be able to do is either access the file inside the container or set the container up so that I can utilize a directory on my NAS. I’ve been trying to figure out how to do this by creating a volume with the container, but it’s not clear and I keep running into roadblocks because when you create a volume it wants a container name and every container name I enter is an invalid path. So I’m stuck.
Certainly there has to be a way to be able to do this so I am asking here.
And would I just use the standard QNAP path to the folder? Those paths above are all local to the container - yes? So how do I specify a path outside the container?
OK. I did something wrong. I took the YML file and modified it to add the local volume to store the data as we discussed. I created this as an application in ContainerStation. But no Application then showed up. But I did have another Docker image show up in Images. So I installed and started that but there is nothing stored in the folder I created on the NAS for holding the data.
Unfortunately, no. The connection is being refused. I am able to use the SimpleHelp admin app to get a backup of my server data. So if I can now figure out how to get that data stored in an accessible folder on my NAS, I should be able to restore from my backup. But my attempt with the YML file didn’t seem to work. So let’s focus on that…
Failed to create application "simplehelp". Error message: operateApp action [--project-name simplehelp up -d --remove-orphans] failed: exit status 1: time="2025-03-27T12:19:37-05:00" level=warning msg="/share/CACHEDEV2_DATA/.qpkg/container-station/data/application/simplehelp/docker-compose.yml: the attributeversion is obsolete, it will be ignored, please remove it to avoid potential confusion" network frontbridge declared as external, but could not be found