DEV-271: added systemd-file as workaround for hazzle with container start order
parent
e6c74d9037
commit
820b162b15
@ -0,0 +1,21 @@
|
||||
#
|
||||
# there is an issue of start order after e.g. rebooting the VM
|
||||
# https://github.com/goharbor/harbor/issues/7008
|
||||
# work around via adding systemd file
|
||||
#
|
||||
#
|
||||
[Unit]
|
||||
Description=Harbor
|
||||
After=docker.service systemd-networkd.service systemd-resolved.service
|
||||
Requires=docker.service
|
||||
Documentation=http://github.com/vmware/harbor
|
||||
|
||||
[Service]
|
||||
Type=simple
|
||||
Restart=on-failure
|
||||
RestartSec=5
|
||||
ExecStart=/usr/bin/docker-compose -f {{ service_base_path }}/{{ inventory_hostname }}/harbor/docker-compose.yml up
|
||||
ExecStop=/usr/bin/docker-compose -f {{ service_base_path }}/{{ inventory_hostname }}/harbor/docker-compose.yml down
|
||||
|
||||
[Install]
|
||||
WantedBy=multi-user.target
|
||||
Loading…
Reference in New Issue