Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker-compose: not all containers start after a server reboot. #20419

Closed
SterhLight opened this issue May 13, 2024 · 1 comment
Closed

docker-compose: not all containers start after a server reboot. #20419

SterhLight opened this issue May 13, 2024 · 1 comment

Comments

@SterhLight
Copy link

Expected behavior:
All containers launched via Docker-compos start after the server is rebooted.
Actual behavior:
Some containers launched via Docker-compos do not start after a server reboot.

03

Steps to reproduce the problem:

  1. Install Harbor via docker-compose
  2. Reboot the server

Versions of the following systems.

  • harbor version: [2.10.0]
  • docker engine version: [24.0.7]
  • docker-compose version: [2.21.0]
@MinerYang
Copy link
Contributor

Hi @SterhLight ,

Please refer to #18704 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants