If you are reporting a problem, please make sure the following information are provided:
1)Version of docker engine and docker-compose.
2)Config files of harbor, you can get them by packaging "harbor.cfg" and files in the same directory, including subdirectory.
located at: https://gist.github.com/8f6be32e626e6e59c4a430eb98f492f3
3)Log files, you can get them by package the /var/log/harbor/ .
located at: https://gist.github.com/828d362973e1b791c0c8f8512b08fbb9
On rebooting my VM, all harbor related services do not restart.
Before reboot
After Reboot
NOTE: This is true with the clair and/or notary installs as well
Could you provide the log files under /var/log/harbor? if the service fails to start there should be some error messages in the latest log files.
should be in the gist log above. Either way I will recapture tonight
upgraded docker-compose to 1.16.0rc1, no help. updated initial bug report
it's because that docker will boot all the no-stopped container but suppose not according to the sequence defined in the docker-compose yml files at the system start up phase.
If you want to ensure Harbor works, you probably need to add some logic in the systemd to control the lifecycle.
Not to be blunt, but shouldn't this already be baked into harbor? from https://github.com/vmware/harbor "An enterprise-class container registry server...". From that perspective, shouldn't harbor be able to recover from and outage, manual reboot, other?
second it fails in such a bad way, not even a docker-compose down; docker-compose up -d can
get it back on it's feet. In fact the only recovery I have right now is docker-compose down. then
rerun sudo ./install [ my options ]
OK i've been looking at harbor 1.2.0rc2
Basic install is much better at recovering from a reboot. All services
still do not restart. but at least it seems I can do a docker-compose start
and they successfully restart without errors. Although it would be extremely
nice if they just all restarted.
Clair and Notary services differ at restarting. Starting to research clair first
So I'm definitely happier with harbor 1.2.0rc2, the docker-compose will start everything without error
But I find it ironic that the docker-compose files say always restart, yet they won't on a reboot or powerhit
There is no update on installation and deployment in v1.2.0-rc2.
Harbor doesn't provide any solution for system reboot/outage so far. But for this, you can definitely use docker-compose down/up to resolve it(If not, please open an issue). No need to perform the install.sh here as all the docker images has already loaded into local system.
The behavior over OS restart is beyond the scope of this project, closing.
Most helpful comment
Not to be blunt, but shouldn't this already be baked into harbor? from https://github.com/vmware/harbor "An enterprise-class container registry server...". From that perspective, shouldn't harbor be able to recover from and outage, manual reboot, other?
second it fails in such a bad way, not even a docker-compose down; docker-compose up -d can
get it back on it's feet. In fact the only recovery I have right now is docker-compose down. then
rerun sudo ./install [ my options ]