tomckay@redhat.com
- Login: tomckay@redhat.com
- Email: tomckay@redhat.com
- Registered on: 02/19/2015
- Last connection: 02/28/2020
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 1 | 1 |
| Reported issues | 0 | 19 | 19 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Container Support | Private Access | 12/06/2019 |
| Crane | Private Access | 02/19/2015 |
| Debian Support | Private Access | 02/19/2015 |
| Docker Support | Private Access | 02/19/2015 |
| File Support | Private Access | 07/17/2017 |
| Migration Plugin | Private Access | 01/14/2020 |
| Nectar | Private Access | 02/19/2015 |
| OSTree Support | Private Access | 02/19/2015 |
| Packaging | Private Access | 02/19/2015 |
| Pulp | Private Access | 02/19/2015 |
| Puppet Support | Private Access | 02/19/2015 |
| Python Support | Private Access | 02/19/2015 |
| RPM Support | Private Access | 02/19/2015 |
Activity
09/06/2018
-
Unsure if relevant/related/problem: I synced the same repo and tag limits in foreman w/ pulp-2.17.0, but the results had zero docker_images. Which is correct, 365 (as in this issue report), zero (as I received in foreman), or something i... Issue #3983: Still seeing lots of docker images when specifying --tagsFirst of all, thank you for the --tags option. I already see significantly less disk usage.
I am not sure if what I am seeing here is a bug, a limitation, or output I am misunderstanding, but:
Before it was possible to set tags I h...
07/23/2018
-
Issue #3880 (CLOSED - WONTFIX): manifest list os and arch attributes on manifests themselvesRelated to https://pulp.plan.io/issues/3137 I see that os/arch is present in the array of manifests associated with a manifest list. I am wondering if that information can/should be stored on the manifests themselves as well.
I unders...
06/04/2018
-
@jortel - It is intentional. Using this paradigm, a user can't upload a manifest that references layers that they don't really have access to. By forcing the layer to exist in the repository already, this forces the initial upload of the... Story #3497: As a user, I can upload skopeo tar that references existing layers.**Motivation:**
To save bandwidth and improve efficiency, layers referred to in a skopeo tar manifest.json that already exist should be allowed to be omitted from the tar.
As I am implementing "docker push" and "skopeo copy docker:...
05/30/2018
-
Note that *skopeo copy dir:* creates a *version* file with contents like "Directory Transport Version: 1.0". Version *1.0* had the *.tar* extensions while version *1.1* does not.
Issue #3703: Update image upload to be compatible with skopeo Directory Transport 1.1Upload of the tar file( from skopeo copy) fails with:
~~~
DKR1018: Layer ff3a5c916c92643ff77519ffa742d3ec61b7f591b6b7504599d95a4a41134e28.tar is not present in the image
~~~
This is due to this change happened in skopeo:
htt...
05/04/2018
-
Foreman will still need crane for smart-proxy. The addition of a docker v2 api to foreman server itself will make it possible to avoid using crane (with some additional work required in foreman) there.
Task #3638: Get crane running in a FIPS enabled environmentThis work might not be necessary. Check with @thomasmckay.
04/27/2018
-
Story #3623 (CLOSED - DUPLICATE): As a user I can sync a registry by whitelisting tags ( Filtered Sync)On many registries there are many, many tags only a subset of which the user cares to download into pulp. This could be for security reasons (older tags with vulnerabilities) or for disk space considerations.
If the list of tags could...
03/16/2018
-
Story #3497 (CLOSED - CURRENTRELEASE): As a user, I can upload skopeo tar that references existing layers.**Motivation:**
To save bandwidth and improve efficiency, layers referred to in a skopeo tar manifest.json that already exist should be allowed to be omitted from the tar.
As I am implementing "docker push" and "skopeo copy docker:...
03/09/2018
-
This usage would also be useful with foreman as well. I can see two ways:
1\. Provide a tag filter up front to limit tags pulled down
2\. Just pull the metadata files for the tags and sync the actual images later (exactly like for RP... Story #3450: As a user I would like to limit the tags we sync for docker repos**Motivation:**
We're currently sync'ing some very large openshift repos from brew. In reality we're only interested in the current 3.9 and newerreleases/tags but we're getting everything, which is weighing in at 1.2TB at present and ...
03/08/2018
-
Story #3443 (CLOSED - WONTFIX): As an API user, I want to upload skopeo tar components individuallyCurrently, to upload a container image directly it is done by using the output of "skopeo copy dir:" and then tar'ing that up. If a client program, in this case foreman, could upload the components individually then it could act as a "do...
02/28/2018
-
Mirror-on-sync would be a very welcome addition to the base user story.
https://pulp.plan.io/issues/2602
Story #3399: As a user I can sync from a docker registryAs a user i can sync v2 complaint specs docker content from a docker registry which is:
\- complaint v2 api specs
\- supports basic auth and token auth
This story is complete when:
\*I can initiate a sync from Docker Registry...
Also available in: Atom
.