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
{{ message }}
This repository has been archived by the owner on Oct 3, 2024. It is now read-only.
I was using the VSCode Toradex extension to deploy/debug a docker container on a Verdin module. This worked. I then had to re-flash the image, but did not click 'Remove device'. When I then tried to deploy to the new machine, I got a strange 'Error response from daemon: Get https://192.168.99.100:5000/v2/: http: server gave HTTP response to HTTPS client' error. This seems to be caused by insecure-registries not being set in /etc/docker/daemon.json; likely because this is done when you connect to a device.
Steps to reproduce:
Connect to a device
Deploy container. This should work.
Re-flash the module
Now you get the error: Error response from daemon: Get https://192.168.99.100:5000/v2/: http: server gave HTTP response to HTTPS client
Workaround:
After re-flashing, click Remove device, then add it again.
Desired behaviour
Ideally, the extension would detect that the initialization procedure (among others setting /etc/docker/daemon.json) has not been completed, and it would first initialize the board if this hasn't happened yet. Alternatively, it could just detect it and throw an error (for example by adding a file /etc/setupdone at the end of the initialization; and throwing an error if this file doesn't exist when we expect it to).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was using the VSCode Toradex extension to deploy/debug a docker container on a Verdin module. This worked. I then had to re-flash the image, but did not click 'Remove device'. When I then tried to deploy to the new machine, I got a strange 'Error response from daemon: Get https://192.168.99.100:5000/v2/: http: server gave HTTP response to HTTPS client' error. This seems to be caused by
insecure-registries
not being set in/etc/docker/daemon.json
; likely because this is done when you connect to a device.Steps to reproduce:
Error response from daemon: Get https://192.168.99.100:5000/v2/: http: server gave HTTP response to HTTPS client
Workaround:
After re-flashing, click
Remove device
, then add it again.Desired behaviour
Ideally, the extension would detect that the initialization procedure (among others setting /etc/docker/daemon.json) has not been completed, and it would first initialize the board if this hasn't happened yet. Alternatively, it could just detect it and throw an error (for example by adding a file /etc/setupdone at the end of the initialization; and throwing an error if this file doesn't exist when we expect it to).
The text was updated successfully, but these errors were encountered: