After upgrading to NAbox 3.5.2 only two docker containers are running....
Any advice?
#Error after updating to Nabox 3.5.2
nimble plover
copper flame
Do you have docker compose ovveride files?
If yes check if they were moved back after the update.
livid moon
I suspect that containers are in a restart loop. Can you check if you have multiple watchdog services running?
ps auxww|grep watch
@scarlet pumice
scarlet pumice
Could be that yes, and also the vmware ovf dns setting maybe
nimble plover
I have two watchdog services:
sm103959:~# ps auxww|grep watch
47 root 0:00 [watchdogd]
3096 root 0:00 {nabox-api-watch} /bin/bash /usr/sbin/nabox-api-watchdog
4414 root 0:00 {nabox-api-watch} /bin/bash /usr/sbin/nabox-api-watchdog
Will check DNS
DNS seems to be working just fine
scarlet pumice
Ok let’s do this
service nabox-api-watchdog stop
dc stop
dc up -d
service nabox-api-watchdog start
Upgrade to nabox 4 😃
nimble plover
/etc/resolv.conf contained only 127.0.0.1.
Changed to our actual DNS sservers and rebooted the host.
That seems to solve the problem.
Not quite....
It tries to look up registry.lab
nimble plover
dc ps works fine, system is collecting and displaying data.
dc down and dc up -d does not work
dc down does work
dc up does not
scarlet pumice
dc images ?
nimble plover
scarlet pumice
Sorry I have to do this from memory. dc images ls ?
nimble plover
No worries! Same output
nimble plover
The system is not working anymore, I tried rebooting. No change.
nimble plover
Ok, I have access tot the environment tomorrow
scarlet mesa
Not quite....
Same issue I have
scarlet pumice
So container images are gone ?
nimble plover
And manually install it
Are you available today?
scarlet pumice
I’m afraid not, on holidays in Japan for a couple of weeks. But I can document the manual update to reload images if they’re gone, which seems weird
nimble plover
Please do! Thanks. And enjoy!
scarlet pumice