Upgrading from SES 6 using an insecure registry fails
This document (000020641) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Enterprise Storage 7
Situation
Pulling container image <ip_address>:5000/registry.suse.com/caasp/v4.5/prometheus-server:2.18.0...
Non-zero exit code 125 from /usr/bin/podman pull <ip_address>:5000/registry.suse.com/caasp/v4.5/prometheus-server:2.18.0
/usr/bin/podman: stderr Trying to pull <ip_address>:5000/registry.suse.com/caasp/v4.5/prometheus-server:2.18.0...
/usr/bin/podman: stderr Get https://<ip_address>:5000/v2/: http: server gave HTTP response to HTTPS client
/usr/bin/podman: stderr Error: unable to pull <ip_address>:5000/registry.suse.com/caasp/v4.5/prometheus-server:2.18.0: Error initializing source docker://<ip_address>:5000/registry.suse.com/caasp/v4.5/prometheus-server:2.18.0: error pinging docker registry <ip_address>:5000: Get https://<ip_address>:5000/v2/: http: server gave HTTP response to HTTPS client
Traceback (most recent call last):
File "/usr/sbin/cephadm", line 6244, in <module>
r = args.func()
File "/usr/sbin/cephadm", line 1451, in _default_image
return func()
File "/usr/sbin/cephadm", line 4000, in command_adopt
_pull_image(args.image)
File "/usr/sbin/cephadm", line 2778, in _pull_image
raise RuntimeError('Failed command: %s' % cmd_str)
RuntimeError: Failed command: /usr/bin/podman pull <ip_address>:5000/registry.suse.com/caasp/v4.5/prometheus-server:2.18.0
Resolution
[[registry]]
prefix = "registry.suse.com"
location = "<ip_or_dns>:5000"
insecure = true
Cause
Additional Information
For more information on the usage of ceph-salt see the Online Documentation .
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000020641
- Creation Date: 20-Apr-2022
- Modified Date:20-Apr-2022
-
- SUSE Enterprise Storage
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com