Containers reset after latest Docker upgrade (17.05.0-0348)

Discussion room for Docker, a lightweight virtualization application that gives you the ability to run thousands of containers created by developers from all over the world on DSM
Forum rules
1) This is a user forum for Synology users to share experience/help out each other: if you need direct assistance from the Synology technical support team, please use the following form:

https://account.synology.com/support/su ... p?lang=enu



2) To avoid putting users' DiskStation at risk, please don't paste links to any patches provided by our Support team as we will systematically remove them. Our Support team will provide the correct patch for your DiskStation model.
gl29
Rookie
Rookie
Posts: 34
Joined: Thu May 30, 2013 12:11 pm

Containers reset after latest Docker upgrade (17.05.0-0348)

Unread post by gl29 » Tue Nov 07, 2017 9:40 am

Hi,

After installing Docker update 17.05.0-0348, I have lost all my containers contents.

I was using InfluxDB and Grafana ... Everything seems to be gone.... like if it was new containers.

The containers seem to be reset !

I did not export / backup my containers ...

Can someone suggest something ?

Thanks
Last edited by gl29 on Tue Nov 07, 2017 11:31 am, edited 1 time in total.

Matthijs Vogt
Trainee
Trainee
Posts: 13
Joined: Fri Apr 25, 2014 1:09 pm

Re: Containers reset after latest Docker upgrade (17.05.0-0348)

Unread post by Matthijs Vogt » Tue Nov 07, 2017 10:40 am

I have the same problem. Any resolution possible?

gl29
Rookie
Rookie
Posts: 34
Joined: Thu May 30, 2013 12:11 pm

Re: Containers reset after latest Docker upgrade (17.05.0-0348)

Unread post by gl29 » Tue Nov 07, 2017 11:31 am

This is bad.
I have contacted Synology and wait for a reply.
I would advice people not to upgrade the Docker Package for now ... Just in case !!!

mightbetrue
Versed
Versed
Posts: 221
Joined: Sun Oct 02, 2016 9:41 am

Re: Containers reset after latest Docker upgrade (17.05.0-0348)

Unread post by mightbetrue » Tue Nov 07, 2017 10:21 pm

Did you install the new package to a different volume?
If so, uninstall again and reinstall to the previously used volume.

That's due to the nature that the docker meta data is stored on the same volume as the app.
A changed volume means no access to the existing meta data on a different volume.

gl29
Rookie
Rookie
Posts: 34
Joined: Thu May 30, 2013 12:11 pm

Re: Containers reset after latest Docker upgrade (17.05.0-0348)

Unread post by gl29 » Tue Nov 07, 2017 10:33 pm

Actually, we had an issue with Volume1 a few weeks ago - broken RAID... Synology managed to save the data but we had to create a new Volume2 ... after deleting Volume1. Volume1 does not show anymore in the DSM interface but still show within the Terminal (Folder "Volume1" ... but it does look empty.
Before Volume1 was deleted and Volume2 created, Synology packages were into a "broken" status. Synology support said packages would get reinstalled once a working Volume would be online ... It was indeed to case once Volume2 was created.

What do you suggest now ?

mightbetrue
Versed
Versed
Posts: 221
Joined: Sun Oct 02, 2016 9:41 am

Re: Containers reset after latest Docker upgrade (17.05.0-0348)

Unread post by mightbetrue » Tue Nov 07, 2017 10:46 pm

what is the output of 'll -a /volume2/@docker/containers' (as root)?

The overlays are stored in /volume2/@docker/aufs this folder should not be empty if Synology recovered ALL you data.
If it is empty, there would be nothing to recover.
Last edited by mightbetrue on Tue Nov 07, 2017 10:49 pm, edited 1 time in total.

gl29
Rookie
Rookie
Posts: 34
Joined: Thu May 30, 2013 12:11 pm

Re: Containers reset after latest Docker upgrade (17.05.0-0348)

Unread post by gl29 » Tue Nov 07, 2017 10:49 pm

root@SYNO-DS1515:~# ll -a /volume2/@docker/containers
total 0
drwx------ 1 root root 384 Oct 28 20:06 .
drwx--x--x 1 root root 122 Nov 7 08:06 ..
drwx------ 1 root root 156 Nov 7 08:07 071bd2f941eb8b479aed4ad1debee4635736a34745145a76743f980d45658c4d
drwx------ 1 root root 178 Nov 7 21:26 0ac1620fc724ad46ac584c0d4a596458a4e78984d0b9d712a0b2978ef8b9664c
drwx------ 1 root root 156 Nov 7 09:25 266bb6ae0a19850a53307d2e6f581519ab800b6f3a4b063f0124f0379f5a9e58

mightbetrue
Versed
Versed
Posts: 221
Joined: Sun Oct 02, 2016 9:41 am

Re: Containers reset after latest Docker upgrade (17.05.0-0348)

Unread post by mightbetrue » Tue Nov 07, 2017 10:50 pm

So you have the meta description for 3 containers. Now the question is if the matching data in the aufs folder exists as well...

Needlerp
Trainee
Trainee
Posts: 10
Joined: Wed Jul 30, 2014 5:24 pm

Re: Containers reset after latest Docker upgrade (17.05.0-0348)

Unread post by Needlerp » Tue Nov 07, 2017 10:53 pm

I'm having exactly the same issue. Both Grafana and InfluxDB reset as though first installed.

Any ideas what can be done to recover the old data? Would be a nightmare if this was lost.

mightbetrue
Versed
Versed
Posts: 221
Joined: Sun Oct 02, 2016 9:41 am

Re: Containers reset after latest Docker upgrade (17.05.0-0348)

Unread post by mightbetrue » Tue Nov 07, 2017 10:56 pm

exactly the same reason with a crashed volume that was recoverd to another volume?

gl29
Rookie
Rookie
Posts: 34
Joined: Thu May 30, 2013 12:11 pm

Re: Containers reset after latest Docker upgrade (17.05.0-0348)

Unread post by gl29 » Tue Nov 07, 2017 11:04 pm

Something very strange.
I own a Synology NAS at home on which I also run 3 containers ...
I did not update Docker on purpose but did run the DSM upgrade ...
Result: I have lost one container (Grafana) but still have InfluxDB one ok (no data lost) ...

It looks like Docker and its containers don't like one of those update.

FYI, I did not have any issues with Volume on my private NAS.

Luckily, I did export the containers before updating this one ...

mightbetrue
Versed
Versed
Posts: 221
Joined: Sun Oct 02, 2016 9:41 am

Re: Containers reset after latest Docker upgrade (17.05.0-0348)

Unread post by mightbetrue » Tue Nov 07, 2017 11:14 pm

A DSM update does not update the Docker page by itself. Though it gets marked immediatly as updateable.

Everything to perists should be mapped into the docker volumes anyway, so even if a container gets messed up, it should be possible to pick up it's state where it was.

gl29
Rookie
Rookie
Posts: 34
Joined: Thu May 30, 2013 12:11 pm

Re: Containers reset after latest Docker upgrade (17.05.0-0348)

Unread post by gl29 » Tue Nov 07, 2017 11:19 pm

I tried to restore Grafana container backed up before the DSM update.
The restoration ran but here again, the container is like brand new. Where are the data ?

Needlerp
Trainee
Trainee
Posts: 10
Joined: Wed Jul 30, 2014 5:24 pm

Re: Containers reset after latest Docker upgrade (17.05.0-0348)

Unread post by Needlerp » Tue Nov 07, 2017 11:27 pm

mightbetrue wrote:exactly the same reason with a crashed volume that was recoverd to another volume?
Mine wasn't due to a crashed volume, there was a DSM update and Docker Package update. It was working fine before the updates, but won't show the original data following restart of my diskstation.

gl29
Rookie
Rookie
Posts: 34
Joined: Thu May 30, 2013 12:11 pm

Re: Containers reset after latest Docker upgrade (17.05.0-0348)

Unread post by gl29 » Tue Nov 07, 2017 11:29 pm

On my home NAS, I have the following:

root@Syno-12-5:~# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
99f29ce982c2 influxdb:latest "/entrypoint.sh influ" 6 weeks ago Up 26 minutes 8083/tcp, 0.0.0.0:32799->8086/tcp influxdb1
954b7b691bfa chronograf:latest "/entrypoint.sh chron" 4 months ago Exited (0) 26 minutes ago chronograf1

root@Syno-12-5:~# ll -a /volume1/@docker/containers
total 20
drwx------ 5 root root 4096 Nov 7 23:13 .
drwx--x--x 13 root root 4096 Jun 12 2016 ..
drwx------ 3 root root 4096 Nov 7 22:47 287cd73784f2bf3a8893617a2f8ada4445e0049208f0122b2723d085e4d7012e
drwx------ 3 root root 4096 Nov 7 22:57 954b7b691bfa1263c289d27bd8fe8a12a85f73265647843c97e5564e61007032
drwx------ 3 root root 4096 Nov 7 23:25 99f29ce982c2e66cda99894463c6b6643fdc4929b8d26d57d788b8f90d173116


The missing Grafana container seems to be the 287cd73784f2bf3a8893617a2f8ada4445e0049208f0122b2723d085e4d7012e folder ...
How can we relink it to the Docker DSM interface ?

Post Reply

Return to “Docker”