Skip to content
This repository has been archived by the owner on Nov 13, 2019. It is now read-only.

Unable to connect #14

Open
gzoller opened this issue Apr 23, 2019 · 0 comments
Open

Unable to connect #14

gzoller opened this issue Apr 23, 2019 · 0 comments

Comments

@gzoller
Copy link

gzoller commented Apr 23, 2019

I'm following the directions to set up/configure and am not able to connect.

I've downloaded a fresh Docker image from DockerHub. Run it. Seems healthy. If I climb inside with docker exec, I can run 'riak ping', 'riak-cs ping' and 'stanchion ping' and all return 'pong'.

I downloaded a fresh install of s3cmd (2.0.2) and configured with this .s3cfg file: (the 2 security keys came from the log output of the running container)

[default]
access_key = OPSBRJYKYIDJQMCDJU6Y
host_base = s3.amazonaws.dev
host_bucket = %(bucket)s.s3.amazonaws.dev
proxy_host = localhost
proxy_port = 8080
secret_key = eUARz8q1KDfap_Dp2t3solbr_8soo5Ubw8UaJA==
signature_v2 = True

The sample docker launch command given in the instructions here create an initial bucket, testbucket, so I thought I should be able to see it.

Running "s3cmd ls" I get this response:

WARNING: Retrying failed request: / (No status line received - the server has closed the connection)
WARNING: Waiting 3 sec...
WARNING: Retrying failed request: / (No status line received - the server has closed the connection)
WARNING: Waiting 6 sec...
^CSee ya!

Am I doing something wrong, or are the instructions not complete?
Thanks,
Greg

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant