aws-nuke icon indicating copy to clipboard operation
aws-nuke copied to clipboard

docker hangs - doesnt complete/return to unix prompt && ignores --no-dry-run

Open ajb1967 opened this issue 4 years ago • 1 comments

hi am running following

nuke.sh

docker run \
    --rm -it \
    -a stdin -a stdout \
    -v /Users/ajb1967/aws-nuke/config/nuke-config.yml:/home/aws-nuke/config.yml \
    -v /Users/ajb1967/.aws:/home/aws-nuke/.aws \
    quay.io/rebuy/aws-nuke:v2.13.0 \
    --no-dry-run \
    --profile cards-demo \
    --config /home/aws-nuke/config.yml

Screenshot 2021-04-21 at 18 03 53

However,

a) command doesn't return to unix prompt (just seems to hang) b) command seems to ignore the --no-dry-run switch

Screenshot 2021-04-21 at 17 59 57

I have tried version 2.15.0 also

Thanks, Andy

ajb1967 avatar Apr 21 '21 17:04 ajb1967

more information - if i continue to wait at the 'apparent' hang, then we get the following error

ERRO[0135] Listing GlobalAcceleratorEndpointGroup failed:
    RequestError: send request failed
    caused by: Post "https://globalaccelerator.us-east-1.amazonaws.com/": dial tcp 92.242.132.24:443: i/o timeout
ERRO[0137] Listing GlobalAccelerator failed:
    RequestError: send request failed
    caused by: Post "https://globalaccelerator.us-east-1.amazonaws.com/": dial tcp 92.242.132.24:443: i/o timeout
ERRO[0138] Listing GlobalAcceleratorListener failed:
    RequestError: send request failed
    caused by: Post "https://globalaccelerator.us-east-1.amazonaws.com/": dial tcp 92.242.132.24:443: i/o timeout

ajb1967 avatar Apr 22 '21 11:04 ajb1967