Cannot start container after upgrade of Container Station

[oyvindo]

When this broke for me the containers were running while it was updating not sure if that has anything to do with it either.

No, I always stop all my container prior to any CS updates - just to be careful, and exactly the same thing happened.
I'm still waiting for an answer from QNAP on my ticket.

Anyway, thanks for the feedback, and I'm glad it worked out for you.

OyvindO

[dynek]

Another option being to create the missing directory.

Error response from daemon: error creating overlay mount to /share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay/ce3df762eb9de8beeb76ea1bb6599359044c8d4a919a4456affd40eeaa4fdb1f/merged: no such file or directory

Code: Select all

mkdir /share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay/ce3df762eb9de8beeb76ea1bb6599359044c8d4a919a4456affd40eeaa4fdb1f/merged

And voila!

[oyvindo]

Another option being to create the missing directory.

That's exactly what I did. But there's no need to create the whole path. It's there already. All you need is the missing folder (the last one).

[jeeper_atx]

oyvindo - thanks for posting your fix!!!

Both Sonarr and NZBGet were not working after the upgrade and wife was not happy!!

Your fix had me back up in five minutes - thanks!

[digitalicecream]

I got it back up and running by creating the missing /merged folder. Everything worked after that.

[dynek]

Another option being to create the missing directory.

That's exactly what I did. But there's no need to create the whole path. It's there already. All you need is the missing folder (the last one).

The command I mentioned is not creating the whole path, just the missing dir

[oyvindo]

The command I mentioned is not creating the whole path, just the missing dir

Creating the whole path is impossible - it already exists. It's only the missing folder that can be created.

[dynek]

What is it that isn't clear? It's not creating the full path, the command I mentioned only creates the missing directory. Can't be clearer than that
If minus (-p) was passed as an argument it would create the full path, even that would be possible.

[fabriziorizzo]

Thank you. This worked perfectly. Damn QNAP...

I think this problem affects many people, including myself.
This is what I did to solve the issue:

1. write down the container ID shown in the error message
2. open up a terminal window to your NAS (I use WinSCP)
3. navigate to the path shown in the error message - and into the container itself (the folder with the long hexadecimal name = Container ID)
In there you should see at least two folders. One named "upper" and another named "work"
4. manually create a new folder named "merged" (without the quotes and use only lowercase letters)

Now your container should start normally.
You have to do this with all your containers.

Let me know if it works for you also.

Viking

I did the same mount point recreation to get things working.

Only downside is that my NAT'd containers shifted down by a port, and the bridged containers found new DHCP addresses. Found them again, and all is well.

[oyvindo]

Thank you. This worked perfectly. ** QNAP...

That's great! Good to hear that it worked for you

[serendrewpity]

#MeToo

...and no, I wasnt bent over my boss' desk...

I just feel like it with this latest update.