Unable to build using rancher-compose and S3 builds

[gmeans]

When trying to 'create' services using rancher-compose, I'm receiving this:

▶ rancher-compose -p <project> create
INFO[0000] Creating service web
INFO[0000] Uploading build for web using provider S3
ERRO[0001] Failed Creating web : :
    status code: 403, request id: []
ERRO[0001] Failed to start: web : :
    status code: 403, request id: []
FATA[0001] :
    status code: 403, request id: []

I had an issue w/ the project name (the directory) having a period in it so had to use the -p flag.

I'm guessing it's having an issue authenticating. I have my env vars for AWS configured correctly and am able to run commands using the AWS CLI. I don't see anything in S3 to indicate rancher uploaded anything however.

[vincent99]

You need an API key for Rancher (from the API & Keys section of the UI underneath the user icon in the header) to use rancher-compose to start containers. It doesn't use AWS credentials to talk to Rancher because we're not Amazon :-)

403 does indeed mean "Forbidden", that is you sent credentials but they were not accepted.

[ibuildthecloud]

@vincent99 We use S3 to upload builds so if you're doing builds you need both AWS and Rancher credentials set up.

[vincent99]

d'oh... I read rancher-compose up, not create. Never mind...

[wlan0]

@gmeans Are you still facing this issue?

If so, could you paste your docker-compose.yml and rancher-compose.yml in here?

[deniseschannon]

@gmeans If you would still like help, please re-open and provide the docker-compose.yml and rancher-compose.yml files.

[lewistaylor]

@gmeans this is not a rancher issue, I had the same problem but it was because the permissions on the bucket created did not match the IAM user I was uploading with.

[ryaninvents]

@lewistaylor would you mind posting what you had to change as far as IAM permissions to get it to work? I'm facing the same issue and documentation seems light on the subject.

[lewistaylor]

@r24y I forget now, but I believe it was on the bucket permissions itself, not the IAM user.

As to how or why it got into that situation, that probably is a separate issue report, but one I haven't felt necessary to start given the problem hasn't happened since.

[ryaninvents]

Thanks. I'll dig a bit and leave what I find here for the next person.