Bug #11392
closed
hammer cli does not need to be uploading docker content when not tiny
Added by Greg Swift over 8 years ago.
Updated almost 6 years ago.
Description
# hammer repository upload-content --path rspec-puppet-el6.tar --id 56
Failed to upload file 'rspec-puppet-el6.tar' to repository. Please check the file and try again.
I'm seeing almost no traffic when I do these (its there, but very low). The first image was 571M, the second was 212M.
However with a 2.4M image....
# hammer repository upload-content --path busybox.tar --id 56
Successfully uploaded file 'busybox.tar'.
For that I saw network traffic immediately and continuously until it was up.
Files
hrmm.. so i take it back.. the 212M file uploaded that time.
- Assignee set to David Davis
- translation missing: en.field_release set to 70
- Triaged changed from No to Yes
Greg, can you attach your foreman-debug or alternatively tail /var/log/foreman/production.log and /var/log/messages (or journalctl) while you try to upload a file that fails?
I'll try to get some data. I don recall seeing anything in the logs.
Also... i apologize for the subject. s/needs/seem/
Tried uploading a 1GB image last night for one of my consumers. here are the last of the logs from when it failed.
- Category changed from Hammer to Container
- Priority changed from Normal to High
- Bugzilla link set to 1275783
- Assignee deleted (
David Davis)
- translation missing: en.field_release changed from 70 to 86
- Assignee set to David Davis
- Status changed from New to Rejected
As of 2.8, pulp no longer supports the uploading of docker images.
the release notes say only docker 2 can't upload.
Unfortunately, docker save does not output Docker v2 content so it is not currently possible to upload Docker v2 content into Pulp. Users who wish to manage Docker v2 content must use the sync feature to bring the objects into Pulp. Docker v1 content can still be uploaded as before.
Ah, you are correct. However, it looks like Katello 3.0 only supports the docker v2 registry API and not the v1 one so that's why we dropped content uploads in 3.0.
Hrm.... so totally breaks part of the usefulness of this feature in our world. the whole point was that users didn't have to run their own registries at all.
Yea, we're evaluating different ways where users can upload/push docker content to Katello without having to run an external registry. We were hoping that docker v2 would have had some way to still export content but that obviously didn't happen. I'll try to update this issue once we have plans though.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by