Cannot start container after upgrade of Container Station
-
- Starting out
- Posts: 13
- Joined: Thu Jun 29, 2017 5:02 am
Cannot start container after upgrade of Container Station
I upgraded Container Station and did a reboot.
Now I cannot start my container anymore, I only get this message:
Anyone got an idea how to fix?
Thanks!
Now I cannot start my container anymore, I only get this message:
Anyone got an idea how to fix?
Thanks!
-
- New here
- Posts: 3
- Joined: Tue May 23, 2017 7:17 pm
Re: Cannot start container after upgrade of Container Station
I am getting the same error for all my containers!! Anybody got an idea how to fix this?
-
- Starting out
- Posts: 22
- Joined: Sun Dec 23, 2007 1:03 am
- Contact:
-
- New here
- Posts: 9
- Joined: Wed Feb 15, 2012 3:53 pm
Re: Cannot start container after upgrade of Container Station
It's incredible,
No update of QNAP works flawlessly, for me it's clear it's a high risk to update any software of QNAP to latest version. I've opened a ticket, do the same please.
No update of QNAP works flawlessly, for me it's clear it's a high risk to update any software of QNAP to latest version. I've opened a ticket, do the same please.
-
- First post
- Posts: 1
- Joined: Mon Jun 22, 2009 3:50 pm
Re: Cannot start container after upgrade of Container Station
same problem here, is there a way to install the previous version?
- Trexx
- Ask me anything
- Posts: 5393
- Joined: Sat Oct 01, 2011 7:50 am
- Location: Minnesota
Re: Cannot start container after upgrade of Container Station
Sounds like you have a garfed container.
Possible Solution:
1) Stop container station
2) Delete all data within the CONTAINER shared folder (you shouldn't be storing any persistant data there anyway)
3) Restart container station
4) Re-pull/setup your docker containers
Other option is tracking down WHICH docker container specifically is using that image number and delete/recreate it.
I have 2 different systems which both upgraded just fine to the new version.
Possible Solution:
1) Stop container station
2) Delete all data within the CONTAINER shared folder (you shouldn't be storing any persistant data there anyway)
3) Restart container station
4) Re-pull/setup your docker containers
Other option is tracking down WHICH docker container specifically is using that image number and delete/recreate it.
I have 2 different systems which both upgraded just fine to the new version.
Paul
Model: TS-877-1600 FW: 4.5.3.x
QTS (SSD): [RAID-1] 2 x 1TB WD Blue m.2's
Data (HDD): [RAID-5] 6 x 3TB HGST DeskStar
VMs (SSD): [RAID-1] 2 x1TB SK Hynix Gold
Ext. (HDD): TR-004 [Raid-5] 4 x 4TB HGST Ultastor
RAM: Kingston HyperX Fury 64GB DDR4-2666
UPS: CP AVR1350
Model:TVS-673 32GB & TS-228a Offline[/color]
-----------------------------------------------------------------------------------------------------------------------------------------
2018 Plex NAS Compatibility Guide | QNAP Plex FAQ | Moogle's QNAP Faq
Model: TS-877-1600 FW: 4.5.3.x
QTS (SSD): [RAID-1] 2 x 1TB WD Blue m.2's
Data (HDD): [RAID-5] 6 x 3TB HGST DeskStar
VMs (SSD): [RAID-1] 2 x1TB SK Hynix Gold
Ext. (HDD): TR-004 [Raid-5] 4 x 4TB HGST Ultastor
RAM: Kingston HyperX Fury 64GB DDR4-2666
UPS: CP AVR1350
Model:TVS-673 32GB & TS-228a Offline[/color]
-----------------------------------------------------------------------------------------------------------------------------------------
2018 Plex NAS Compatibility Guide | QNAP Plex FAQ | Moogle's QNAP Faq
-
- Starting out
- Posts: 22
- Joined: Sun Dec 23, 2007 1:03 am
- Contact:
Re: Cannot start container after upgrade of Container Station
Four containers did not break themselves. Also says the Wordpress one is running and it is not. This is definitely an issue with the upgrade. Will say, normally upgrades have gone fine for me. Till now.
QNAP 209-Pro
- Trexx
- Ask me anything
- Posts: 5393
- Joined: Sat Oct 01, 2011 7:50 am
- Location: Minnesota
Re: Cannot start container after upgrade of Container Station
That very well may be, but I guess it comes down to do you want to try and fix it vs. talk about QNAP breaking it??ahbrown41 wrote:Four containers did not break themselves. Also says the Wordpress one is running and it is not. This is definitely an issue with the upgrade. Will say, normally upgrades have gone fine for me. Till now.
Sometimes it feels like this board turns into more of a gripe session about all the things that QNAP screws up... and just like all companies, they aren't perfect. But the purpose of the board is to share issues (with the appropriate amount of relevant configuration detail) to work towards solutions.
Just as an FYI - I do all my container setup via command line, and persist my data in a separate directory, so I can recreate all my containers in about 2 minutes via copy/paste.
Paul
Model: TS-877-1600 FW: 4.5.3.x
QTS (SSD): [RAID-1] 2 x 1TB WD Blue m.2's
Data (HDD): [RAID-5] 6 x 3TB HGST DeskStar
VMs (SSD): [RAID-1] 2 x1TB SK Hynix Gold
Ext. (HDD): TR-004 [Raid-5] 4 x 4TB HGST Ultastor
RAM: Kingston HyperX Fury 64GB DDR4-2666
UPS: CP AVR1350
Model:TVS-673 32GB & TS-228a Offline[/color]
-----------------------------------------------------------------------------------------------------------------------------------------
2018 Plex NAS Compatibility Guide | QNAP Plex FAQ | Moogle's QNAP Faq
Model: TS-877-1600 FW: 4.5.3.x
QTS (SSD): [RAID-1] 2 x 1TB WD Blue m.2's
Data (HDD): [RAID-5] 6 x 3TB HGST DeskStar
VMs (SSD): [RAID-1] 2 x1TB SK Hynix Gold
Ext. (HDD): TR-004 [Raid-5] 4 x 4TB HGST Ultastor
RAM: Kingston HyperX Fury 64GB DDR4-2666
UPS: CP AVR1350
Model:TVS-673 32GB & TS-228a Offline[/color]
-----------------------------------------------------------------------------------------------------------------------------------------
2018 Plex NAS Compatibility Guide | QNAP Plex FAQ | Moogle's QNAP Faq
-
- New here
- Posts: 3
- Joined: Tue May 23, 2017 7:17 pm
Re: Cannot start container after upgrade of Container Station
I have 4 containers that also all broke with the update - never happened before. Was hoping not to have to recreate all containers, but looks like there is no option. Hope in future updates are checked better for ALL use cases. At least 4 people with same issue does not sound as though this is something any person did themselves.
- Trexx
- Ask me anything
- Posts: 5393
- Joined: Sat Oct 01, 2011 7:50 am
- Location: Minnesota
Re: Cannot start container after upgrade of Container Station
Not suggesting that it is something people did themselves, but without any useful information being provided such as NAS Model, QTS Version & Build, Container Station version (before and after upgrade), which containers were installed, etc. there isn't really any useful information in these posts other than something broke.MadMitch75 wrote:I have 4 containers that also all broke with the update - never happened before. Was hoping not to have to recreate all containers, but looks like there is no option. Hope in future updates are checked better for ALL use cases. At least 4 people with same issue does not sound as though this is something any person did themselves.
Paul
Model: TS-877-1600 FW: 4.5.3.x
QTS (SSD): [RAID-1] 2 x 1TB WD Blue m.2's
Data (HDD): [RAID-5] 6 x 3TB HGST DeskStar
VMs (SSD): [RAID-1] 2 x1TB SK Hynix Gold
Ext. (HDD): TR-004 [Raid-5] 4 x 4TB HGST Ultastor
RAM: Kingston HyperX Fury 64GB DDR4-2666
UPS: CP AVR1350
Model:TVS-673 32GB & TS-228a Offline[/color]
-----------------------------------------------------------------------------------------------------------------------------------------
2018 Plex NAS Compatibility Guide | QNAP Plex FAQ | Moogle's QNAP Faq
Model: TS-877-1600 FW: 4.5.3.x
QTS (SSD): [RAID-1] 2 x 1TB WD Blue m.2's
Data (HDD): [RAID-5] 6 x 3TB HGST DeskStar
VMs (SSD): [RAID-1] 2 x1TB SK Hynix Gold
Ext. (HDD): TR-004 [Raid-5] 4 x 4TB HGST Ultastor
RAM: Kingston HyperX Fury 64GB DDR4-2666
UPS: CP AVR1350
Model:TVS-673 32GB & TS-228a Offline[/color]
-----------------------------------------------------------------------------------------------------------------------------------------
2018 Plex NAS Compatibility Guide | QNAP Plex FAQ | Moogle's QNAP Faq
-
- New here
- Posts: 8
- Joined: Sat Dec 29, 2012 11:31 pm
Re: Cannot start container after upgrade of Container Station
Download the last good version (1.8.3031) and install manually.Gigadwerg wrote:same problem here, is there a way to install the previous version?
https://download.qnap.com/QPKG/containe ... 31_x86.zip
TS-251
-
- Starting out
- Posts: 13
- Joined: Thu Jun 29, 2017 5:02 am
Re: Cannot start container after upgrade of Container Station
I agree the OP lack this information, I was a bit frustrated when I wrote it. My bad.Trexx wrote:Not suggesting that it is something people did themselves, but without any useful information being provided such as NAS Model, QTS Version & Build, Container Station version (before and after upgrade), which containers were installed, etc. there isn't really any useful information in these posts other than something broke.MadMitch75 wrote:I have 4 containers that also all broke with the update - never happened before. Was hoping not to have to recreate all containers, but looks like there is no option. Hope in future updates are checked better for ALL use cases. At least 4 people with same issue does not sound as though this is something any person did themselves.
My NAS Is a TVS-471 and running 4.3.4.0644
The CS running before was the latest one (at that time). Probably the one that is linked to above this post.
I only have one container and it is eclipse-mosquitto:latest container
-
- Starting out
- Posts: 13
- Joined: Thu Jun 29, 2017 5:02 am
Re: Cannot start container after upgrade of Container Station
This didnt help for me. I got the same overlay error..orogers wrote:Download the last good version (1.8.3031) and install manually.Gigadwerg wrote:same problem here, is there a way to install the previous version?
https://download.qnap.com/QPKG/containe ... 31_x86.zip
- Trexx
- Ask me anything
- Posts: 5393
- Joined: Sat Oct 01, 2011 7:50 am
- Location: Minnesota
Re: Cannot start container after upgrade of Container Station
Oh I know the frustrated feeling.. been dealing with a quirky NAS issue for 2+ months, and had NW headaches this morning.Freddy_L wrote: I agree the OP lack this information, I was a bit frustrated when I wrote it. My bad.
My NAS Is a TVS-471 and running 4.3.4.0644
The CS running before was the latest one (at that time). Probably the one that is linked to above this post.
I only have one container and it is eclipse-mosquitto:latest container
Here is a good guide (I would call it almost mandatory reading) for using Container Station the best way possible.
https://blog.linuxserver.io/2017/09/17/ ... s-on-qnap/
Paul
Model: TS-877-1600 FW: 4.5.3.x
QTS (SSD): [RAID-1] 2 x 1TB WD Blue m.2's
Data (HDD): [RAID-5] 6 x 3TB HGST DeskStar
VMs (SSD): [RAID-1] 2 x1TB SK Hynix Gold
Ext. (HDD): TR-004 [Raid-5] 4 x 4TB HGST Ultastor
RAM: Kingston HyperX Fury 64GB DDR4-2666
UPS: CP AVR1350
Model:TVS-673 32GB & TS-228a Offline[/color]
-----------------------------------------------------------------------------------------------------------------------------------------
2018 Plex NAS Compatibility Guide | QNAP Plex FAQ | Moogle's QNAP Faq
Model: TS-877-1600 FW: 4.5.3.x
QTS (SSD): [RAID-1] 2 x 1TB WD Blue m.2's
Data (HDD): [RAID-5] 6 x 3TB HGST DeskStar
VMs (SSD): [RAID-1] 2 x1TB SK Hynix Gold
Ext. (HDD): TR-004 [Raid-5] 4 x 4TB HGST Ultastor
RAM: Kingston HyperX Fury 64GB DDR4-2666
UPS: CP AVR1350
Model:TVS-673 32GB & TS-228a Offline[/color]
-----------------------------------------------------------------------------------------------------------------------------------------
2018 Plex NAS Compatibility Guide | QNAP Plex FAQ | Moogle's QNAP Faq
-
- Starting out
- Posts: 13
- Joined: Thu Jun 29, 2017 5:02 am
Re: Cannot start container after upgrade of Container Station
Trexx wrote:Sounds like you have a garfed container.
Possible Solution:
1) Stop container station
2) Delete all data within the CONTAINER shared folder (you shouldn't be storing any persistant data there anyway)
3) Restart container station
4) Re-pull/setup your docker containers
Other option is tracking down WHICH docker container specifically is using that image number and delete/recreate it.
I have 2 different systems which both upgraded just fine to the new version.
Would you mind explaining step 2 more in detail?
It is good for you that you run everything using console and that might be the preferred way. But for us that are not that experienced in Docker etc we rely on the official tools given.
Thank you