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 downding as ./scripts/pi-setup/auto-install.sh , below errors tooks out. Please give a help, thanks
update-docker-images.sh: Downloading proxy and db Docker images
WARN[0000] The "BACKEND_FILEPATH_ON_HOST" variable is not set. Defaulting to a blank string.
[+] Pulling 2/2
✘ proxy Error context canceled 15.1s
✘ db Error Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) 15.1s
Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Steps to reproduce the behavior
No response
Expected behavior
Environment will be set OK
Log files
No response
PICS file
No response
Screenshots
No response
Environment
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
When I downding as ./scripts/pi-setup/auto-install.sh , below errors tooks out. Please give a help, thanks
update-docker-images.sh: Downloading proxy and db Docker images
WARN[0000] The "BACKEND_FILEPATH_ON_HOST" variable is not set. Defaulting to a blank string.
[+] Pulling 2/2
✘ proxy Error context canceled 15.1s
✘ db Error Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) 15.1s
Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Steps to reproduce the behavior
No response
Expected behavior
Environment will be set OK
Log files
No response
PICS file
No response
Screenshots
No response
Environment
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: