Upload to container registry fails with 403 when S3 storage is used
If I push to my container registry I receive this error:
f042d6df1be9: Pushing [==================================================>] 12.5 MB
c2195e6e235f: Pushing [====================> ] 13.68 MB/33.25 MB
ed1f96f04c96: Pushing [==================================> ] 13.39 MB/19.2 MB
f645386f1bf6: Pushing [==================================================>] 9.216 kB
b506a2df4ccd: Pushing [==================================> ] 10.49 MB/15.36 MB
6d9adc4dcda7: Pushing [==================================================>] 426 kB
d099a5b1211c: Pushing [=====> ] 35.28 MB/349.2 MB
5f70bf18a086: Waiting
3f647195edaf: Waiting
4e69899d6e22: Waiting
bb966b50623d: Waiting
fb49515ec5d8: Waiting
bd750002938c: Waiting
917c0fc99b35: Waiting
error parsing HTTP 403 response body: unexpected end of JSON input: ""
Command used to push:
$ docker push gitlab.example.com:4567/example/example-repo
Registry config:
registry_external_url 'https://gitlab.example.com:4567'
gitlab_rails['registry_enabled'] = true
gitlab_rails['registry_host'] = "gitlab.example.com"
#gitlab_rails['registry_port'] = "4567"
gitlab_rails['registry_api_url'] = "http://localhost:5000"
gitlab_rails['gitlab_default_projects_features_container_registry'] = false
registry['enable'] = true
registry['storage'] = {
's3' => {
'accesskey' => '',
'secretkey' => '',
'bucket' => 'example.bucket',
'region' => 'us-west-2'
}
}
Misc Info:
- I have logged into my registry successfully
- Parts of the upload can be seen in the S3 bucket
- Running Gitlab 8.9.6-ee
- I am able to successfully push the image to the registry if I do not set the storage option to S3