-
Notifications
You must be signed in to change notification settings - Fork 30
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
registry container stuck in "Created" status #267
Comments
Several servers have this problem.
|
I also asked appliance team to help me solve this problem fundamentally so that the registry container can always run. |
Hey @yuchao4x.
|
[root@8d141 ~]# podman ps [root@8d141 ~]# systemctl status start-local-registry.service [root@8d141 ~]# ll /run/start-local-registry.service.ctr-id [root@8d141 ~]# journalctl -f -b -u start-local-registry.service ========= |
Thanks @wzhu2x. Can you please also attach the logs of the existing pod?
|
[root@sno paas]# podman ps |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
I installed a OCP 4.16.0 on Dell R750 server with appliance, and using the own registry
But for some reason, the status of the registry container changed from Up to Created, and then it could not be started automaticly.
I understood that the setup-local-registry service would automatically start it, but it did not. The service log is as follows:
The text was updated successfully, but these errors were encountered: