Container station don't start after upgrade to V1.8.3062

[sunnyl]

Just did the downgrade as well.

How do you actually check the version of what you've installed?

[neothematrix]

Just did the downgrade as well.

How do you actually check the version of what you've installed?

I think you can just open the Container Station inside the "App Center" it will show the currently installed version and the latest available version (if it's not the same as the one you have installed)

[confuzed]

Just here to add another "me too" to this thread, docker is trashed following the latest update to the container station app. I'll be trying the downgrade posted above soon.

[neothematrix]

I suggest we all open a ticket to QNAP support (I did already), I'm not sure they monitor this forum

[limonoah]

Same issue.

[dolbyman]

I suggest we all open a ticket to QNAP support (I did already), I'm not sure they monitor this forum

exactly .. open tickets, QNAP does NOT monitor this forum

[Martijn]

I downloaded a slightly older version (1.8.3031) and it's working fine now. Will wait for the next release before upgrading.

https://download.qnap.com/QPKG/containe ... 31_x86.zip

Same here! Thanks for the link @orogers!

Noticed that while V1.8.3062 fails to start my CPU usage went up to a constant ~40% vs normally 0-5%. For those who haven't downgraded it may be worth shutting down container-station for the time being.

[napper0]

I downloaded a slightly older version (1.8.3031) and it's working fine now. Will wait for the next release before upgrading.

https://download.qnap.com/QPKG/containe ... 31_x86.zip

*Edit: Eh, well, Browser Station won't start until you do the version string edit in /etc/config/qpkg.conf (make it 1.8.3062) else starting Browser Station will try to update Container Station at the same time.

I registered specially to say THANK YOU!
I was troubleshooting for hours, thinking I had borked it myself. 5 minutes later, I'm up and running again. Thanks for sharing!

[kmrodgers]

Many thanks to orogers for figuring this out. Very disappointed in QNAP QA to deploy such a broken "update"...

[petur]

Philippe,

Mine failed in another way:

Code: Select all

could not create bridge network for id
8263739f937d677550b35c38de8f06948372a6a733078688e9f9879b9fd2b319
bridge name lxcbr0 while booting up from persistent state: Failed to
program NAT chain: Failed to inject DOCKER in PREROUTING chain:
iptables failed: iptables --wait -t nat -A PREROUTING -m addrtype
--dst-type LOCAL -j DOCKER: iptables: No chain/target/match by that
name.
(exit status 1)
INFO[2018-05-26T16:26:33.331262130+02:00] Default bridge (docker0) is
assigned with an IP address 10.0.5.0/24. Daemon option --bip can be
used to set a preferred IP address
Error starting daemon: Error initializing network controller: Error
creating default "bridge" network: Failed to program NAT chain: Failed
to inject DOCKER in PREROUTING chain: iptables failed: iptables --wait
-t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER: iptables:
No chain/target/match by that name.

wiping the container folder and reinstalling the containers fixed it for me

[slally]

dockerd is started on my setup. The problem is that the new version of Container Station has it listening on unix:///var/run/system-docker.sock While docker and the Container Station gui are trying to connect via unix:///var/run/docker.sock Think I'm just going to do the downgrade as well. Thanks to those who submitted tickets.

[mrfroggg]

same issue!

[Trexx]

same issue!

Did you submit a helpdesk ticket with Qnap?


Sent from my iPhone using Tapatalk

[Guapo81]

Got answer from QNAP support:

Dear customer,
Please download the container station and let me know the results.
Kind regards,
QNAP support

Downloaded latest version from QNAP site, essentially same as answers above, they rolled it back a version and put the app in Beta.
At least all is working fine again and other apps are not complaining about latest version of container station anymore.

[mazhead]

dockerd is started on my setup. The problem is that the new version of Container Station has it listening on unix:///var/run/system-docker.sock While docker and the Container Station gui are trying to connect via unix:///var/run/docker.sock Think I'm just going to do the downgrade as well. Thanks to those who submitted tickets.

That is not totally true, there are 2 docker daemons running on QNAP, one is the container station: unix:///var/run/docker.sock and the 2nd one is actually a system docker (for example notes station 3 is running under this daemon) and is located unix:///var/run/system-docker.sock.