-
Notifications
You must be signed in to change notification settings - Fork 52
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
unable to start mirror registry #12
Comments
With debug logs: TASK [mirror_registry : Enable container-mirror-registry on boot and start it] **************************************************************************************************************** PLAY RECAP ************************************************************************************************************************************************************************************ 2673 1594992403.39457: RUNNING CLEANUP |
Ran into the following error when attempting to use mirror registry:
TASK [mirror_registry : Enable container-mirror-registry on boot and start it] ****************************************************************************************************************
fatal: [helper]: FAILED! => {"changed": false, "msg": "Unable to start service container-mirror-registry: Job for container-mirror-registry.service failed because the control process exited with error code.\nSee "systemctl status container-mirror-registry.service" and "journalctl -xe" for details.\n"}
PLAY RECAP ************************************************************************************************************************************************************************************
helper : ok=10 changed=0 unreachable=0 failed=1 skipped=6 rescued=0 ignored=0
[root@helper-host openshift-auto-upi]# systemctl status container-mirror-registry.service
● container-mirror-registry.service - Podman container-6e79cd4be0da3086a24806aa74851677040af5cbbc01b60cab5c9ff480a351e6.service
Loaded: loaded (/etc/systemd/system/container-mirror-registry.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2020-07-17 09:18:52 EDT; 6s ago
Docs: man:podman-generate-systemd(1)
Process: 12371 ExecStart=/usr/bin/podman start 6e79cd4be0da3086a24806aa74851677040af5cbbc01b60cab5c9ff480a351e6 (code=exited, status=125)
Main PID: 10694 (code=exited, status=0/SUCCESS)
Jul 17 09:18:52 helper-host.autoupi.example.com systemd[1]: container-mirror-registry.service: Control process exited, code=exited status=125
Jul 17 09:18:52 helper-host.autoupi.example.com systemd[1]: container-mirror-registry.service: Failed with result 'exit-code'.
Jul 17 09:18:52 helper-host.autoupi.example.com systemd[1]: Failed to start Podman container-6e79cd4be0da3086a24806aa74851677040af5cbbc01b60cab5c9ff480a351e6.service.
Jul 17 09:18:52 helper-host.autoupi.example.com systemd[1]: container-mirror-registry.service: Service RestartSec=100ms expired, scheduling restart.
Jul 17 09:18:52 helper-host.autoupi.example.com systemd[1]: container-mirror-registry.service: Scheduled restart job, restart counter is at 5.
Jul 17 09:18:52 helper-host.autoupi.example.com systemd[1]: Stopped Podman container-6e79cd4be0da3086a24806aa74851677040af5cbbc01b60cab5c9ff480a351e6.service.
Jul 17 09:18:52 helper-host.autoupi.example.com systemd[1]: container-mirror-registry.service: Start request repeated too quickly.
Jul 17 09:18:52 helper-host.autoupi.example.com systemd[1]: container-mirror-registry.service: Failed with result 'exit-code'.
Jul 17 09:18:52 helper-host.autoupi.example.com systemd[1]: Failed to start Podman container-6e79cd4be0da3086a24806aa74851677040af5cbbc01b60cab5c9ff480a351e6.service.
The text was updated successfully, but these errors were encountered: