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 11, 2023. It is now read-only.
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
AWS
Issue:
Using wget on the default console busy box in rancher os version 1.1.3.
Trying to use wget to make standard web requests that responds with an unexpected error: wget: error getting response: Connection reset by peer
Problem only present for 1.1.3 version of busy box, tested with other consoles ubuntu, centos and using docker with alpine based image on a AWS instance running the current version discussed.
This is crucial for our cattle labelling scheme, which is how we manage the cleanup of disconnected AWS instances, so is proving rather problematic and stopping us upgrading and using the latest C5 instance types.
This can even be proven using telnet from the same failing instance running busy box, which works successfully: (printf 'GET /latest/meta-data/instance-id HTTP/1.0\r\n'; sleep 1) | telnet 169.254.169.254 80
Example wget command (AWS static IP for Metadata service) FAILING: wget -qO- http://169.254.169.254/latest/meta-data/placement/availability-zone
Known working version
Previous known working rancher version: v1.1.0
RancherOS Version: (ros os version)
v1.1.3
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
AWS
Issue:
wget
on the default console busy box in rancher os version 1.1.3.wget
to make standard web requests that responds with an unexpected error:wget: error getting response: Connection reset by peer
ubuntu
,centos
and usingdocker
withalpine
based image on a AWS instance running the current version discussed.This is crucial for our cattle labelling scheme, which is how we manage the cleanup of disconnected AWS instances, so is proving rather problematic and stopping us upgrading and using the latest C5 instance types.
This can even be proven using telnet from the same failing instance running busy box, which works successfully:
(printf 'GET /latest/meta-data/instance-id HTTP/1.0\r\n'; sleep 1) | telnet 169.254.169.254 80
Example wget command (AWS static IP for Metadata service) FAILING:
wget -qO- http://169.254.169.254/latest/meta-data/placement/availability-zone
Known working version
Previous known working rancher version: v1.1.0
Related issues
wget is broken against AWS metadata: #2216
alpine:3.6 is unable to wget http://google.com: gliderlabs/docker-alpine#344
The text was updated successfully, but these errors were encountered: