(Suggestion) Easier method to remove images about reg HOT 14 CLOSED

On Wed, Mar 1, 2017 at 3:04 PM, Francis Lavoie ***@***.***> wrote: Yeah I know that, but how do I get the digest for the argument to rm? I want to delete a specific tagged image, for example something like reg rm repo/image:2.0.1 but it looks like I need to give a digest like reg rm ***@***.***:a3ed95caeb02ffe68cdd9fd8440668 0ae93d633cb16422d00e8a7c22955b46d4 but I don't have a way to find out the digest of that tag. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABYNbEncHhGTzpxOU9KY_BRybIGoI-Evks5rhfmAgaJpZM4MQUct> .

On Wed, Mar 1, 2017 at 2:58 PM, Francis Lavoie ***@***.***> wrote: This might be my fault, but I only get v1 schemas from reg manifest <image>. Is there any way to force getting v2 schemas so I can get the image digest and remove it? Otherwise I'm not sure how I'm supposed to remove images. Deleting "fsLayers" doesn't seem like a good idea. Thanks! 😄 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABYNbFtKwnK_7C9t3P_k8IsuxUMmVHLjks5rhff_gaJpZM4MQUct> .

On Wed, Mar 1, 2017 at 3:07 PM, Jessica Frazelle ***@***.***> wrote: hmm ya so if its only returning v1 then that might mean that image doesnt have a v2 manifest, because the function tries to get v2 then defaults to getting v1... let me think haha On Wed, Mar 1, 2017 at 3:04 PM, Francis Lavoie ***@***.***> wrote: > Yeah I know that, but how do I get the digest for the argument to rm? I > want to delete a specific tagged image, for example something like reg > rm repo/image:2.0.1 but it looks like I need to give a digest like reg > rm ***@***.***:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb1 > 6422d00e8a7c22955b46d4 but I don't have a way to find out the digest of > that tag. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#5 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ABYNbEncHhGTzpxOU9KY_BRybIGoI-Evks5rhfmAgaJpZM4MQUct> > . > -- Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu <http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3>

On Wed, Mar 1, 2017 at 3:09 PM, Jessica Frazelle ***@***.***> wrote: so if you run in debug, you can get the ref: ``` $ reg -d -r r.j3ss.co manifest chrome:latest 2017/03/01 15:08:23 registry.ping url=https://r.j3ss.co/v2/ 2017/03/01 15:08:24 registry.manifests url=https://r.j3ss.co/v2/ chrome/manifests/latest repository=chrome ref=latest 2017/03/01 15:08:24 ref: sha256:fbb5be37719eed09f1f3afd83a6526 e8b720c64b7c20b2ee2ddba203e9dd9623 2017/03/01 15:08:24 registry.manifests url=https://r.j3ss.co/v2/ chrome/manifests/latest repository=chrome ... ``` On Wed, Mar 1, 2017 at 3:07 PM, Jessica Frazelle ***@***.***> wrote: > hmm ya so if its only returning v1 then that might mean that image doesnt > have a v2 manifest, because the function tries to get v2 then defaults to > getting v1... let me think haha > > On Wed, Mar 1, 2017 at 3:04 PM, Francis Lavoie ***@***.***> > wrote: > >> Yeah I know that, but how do I get the digest for the argument to rm? I >> want to delete a specific tagged image, for example something like reg >> rm repo/image:2.0.1 but it looks like I need to give a digest like reg >> rm ***@***.***:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb1 >> 6422d00e8a7c22955b46d4 but I don't have a way to find out the digest of >> that tag. >> >> — >> You are receiving this because you commented. >> Reply to this email directly, view it on GitHub >> <#5 (comment)>, or mute >> the thread >> <https://github.com/notifications/unsubscribe-auth/ABYNbEncHhGTzpxOU9KY_BRybIGoI-Evks5rhfmAgaJpZM4MQUct> >> . >> > > > > -- > > > Jessie Frazelle > 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 > pgp.mit.edu > <http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3> > -- Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu <http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3>

On Wed, Mar 1, 2017 at 3:14 PM, Francis Lavoie ***@***.***> wrote: I can envision doing something like reg tags repo/image | sort -V | head -n 5 | xargs -L 1 reg rmtag or something crazy like that — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABYNbBk0oCk-p0Zz_AImsafyz9hE17kDks5rhfvxgaJpZM4MQUct> .

lol yeah On Wed, Mar 1, 2017 at 3:14 PM, Francis Lavoie ***@***.***> wrote: > I can envision doing something like reg tags repo/image | sort -V | head > -n 5 | xargs -L 1 reg rmtag or something crazy like that > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#5 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ABYNbBk0oCk-p0Zz_ AImsafyz9hE17kDks5rhfvxgaJpZM4MQUct> > . > -- Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu <http://pgp.mit.edu/pks/lookup?op=get&search= 0x18F3685C0022BFF3> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABYNbP77NaGfqDZZBPT35zFN7J3TE3EOks5rhf2YgaJpZM4MQUct> .