Open matthughes opened 10 years ago
@matthughes you are using glance with swift + file system, right?
I was actually trying to just use the swift option.
https://github.com/dotcloud/docker-registry/blob/master/config/config_sample.yml
# This flavor is for storing images in Openstack Swift
swift: &swift
storage: swift
storage_path: _env:STORAGE_PATH:/registry
# keystone authorization
swift_authurl: _env:OS_AUTH_URL
swift_container: _env:OS_CONTAINER
swift_user: _env:OS_USERNAME
swift_password: _env:OS_PASSWORD
swift_tenant_name: _env:OS_TENANT_NAME
swift_region_name: _env:OS_REGION_NAME
@matthughes By any chance, would you be willing to help writing a .travis.yml file that would install and configure swift?
That would let unit tests be run on travis against an actual swift server and would help us reproduce / fix your problem.
That would be there: https://github.com/bacongobbler/docker-registry-driver-swift/blob/master/.travis.yml
If you would need help converting your installation steps into travis lingo, ask me (on irc: channel docker-dev or by mail).
Now, from your logs:
ClientException: Object PUT failed: http://swiftds:8080/swift/v1/docker-registry-retry/registry/images/7064731afe90d78da2c117d64a1221c826234cd7145fd330ae7e207ff5606980/json 404 Not Found NoSuchBucket
Is it possible you have not configured swift container properly?
Thanks!
@bacongobbler ping - any idea on this? Looks like it's in your garden :-)
Sounds like you need to create the docker-registry-retry
bucket from the log you pointed out. You have to create them beforehand unlike s3, which creates them on the fly.
@matthughes did my above comment solve it for you?
ping @matthughes
Running the latest registry with a swift storage, I get 500 when it actually tries to push the images. It accepts the snapshots and I can see them in my swift store, so I know the credentials, connection info is correct.
Client Logs
Server Logs