You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to pull a container image from an insecure registry using plain-http, I receive an error stating that an HTTPS client is being used. For example with this command: ctr image pull --plain-http --local="false" 192.168.139.3:5002/net-monitor:v1
I receive the following error: ctr: rpc error: code = Unknown desc = failed to resolve image: failed to do request: Head "https://192.168.139.3:5002/v2/net-monitor/manifests/v1": http: server gave HTTP response to HTTPS client
Is the restriction of using only the HTTPS protocol intentional or is this a bug?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When I try to pull a container image from an insecure registry using plain-http, I receive an error stating that an HTTPS client is being used. For example with this command:
ctr image pull --plain-http --local="false" 192.168.139.3:5002/net-monitor:v1
I receive the following error:
ctr: rpc error: code = Unknown desc = failed to resolve image: failed to do request: Head "https://192.168.139.3:5002/v2/net-monitor/manifests/v1": http: server gave HTTP response to HTTPS client
Is the restriction of using only the HTTPS protocol intentional or is this a bug?
Beta Was this translation helpful? Give feedback.
All reactions