What is the problem you're trying to solve
I've tried to push/pull test for using ctr in my custom registry service.
Even though success to push/pull with latest tag, I failed to push with 'non-latest' tag
(I think ctr doesn't support docker's tag command)
Describe the solution you'd like
Can I change the tag name using 'ctr command' or push it to a 'non-latest' tag?
Additional context
Below are my logs
[root@~:/root] docker images | grep 5001
sds.redii.net/sdspaas/fluent-bit 1.2.2 075001dca2c6 7 months ago 53.2MB
localhost:5001/httpd alpine e930b133a978 11 months ago 128MB
localhost:5001/busybox latest 00950dad8965 2 years ago 12.3MB
[root@~:/root]
[root@~:/root] ctr images push localhost:5001/busybox
ctr: unable to resolve image to manifest: image "localhost:5001/busybox": not found
[root@~:/root] ctr images push localhost:5001/busybox:latest
manifest-sha256:06459888027d8d290b70759e69a46a5032779e78038d7b67b2f98db0d32b70d1: done |++++++++++++++++++++++++++++++++++++++|
layer-sha256:e3debd4dac47035b84218f66a1792329bbe46a306ac19518712e955308d5aca5: done |++++++++++++++++++++++++++++++++++++++|
config-sha256:00950dad8965b32c9a0f4e6d369e848555e0434e2d9c804247b3a04f1e7507e5: done |++++++++++++++++++++++++++++++++++++++|
layer-sha256:6d987f6f42797d81a318c40d442369ba3dc124883a0964d40b0c8f4f7561d913: done |++++++++++++++++++++++++++++++++++++++|
layer-sha256:dbb0e1305741dc552e11e8a226195b68aeab0f1013c7f2e6e9268b04e6ed2327: done |++++++++++++++++++++++++++++++++++++++|
elapsed: 0.1 s total: 0.0 B (0.0 B/s)
[root@~:/root]
[root@~:/root] ctr images push localhost:5001/httpd
ctr: unable to resolve image to manifest: image "localhost:5001/httpd": not found
[root@~:/root]
[root@~:/root] ctr images push localhost:5001/httpd:alpine
ctr: unable to resolve image to manifest: image "localhost:5001/httpd:alpine": not found
[root@~:/root]
[root@~:/root]
[root@~:/root]
[root@~:/root] docker push localhost:5001/httpd:alpine
The push refers to repository [localhost:5001/httpd]
e771280fc920: Pushed
1b02fd077f13: Pushed
fb6547044b4e: Pushed
641a07ed2436: Pushed
bcf2f368fe23: Pushed
alpine: digest: sha256:98bbe4bcfebbcf471cb0b32caf757def8f55b7cf4d515a168c90101f2e92d46f size: 1362
[root@~:/root]
thanks for reporting. could you mind to show the result ctr image ls | grep 5001 ? I am not sure that you pulled the image into your local ..... docker doesn't have used containerd to manage image store yet.
thanks for reporting. could you mind to show the result
ctr image ls | grep 5001? I am not sure that you pulled the image into your local ..... docker doesn't have used containerd to manage image store yet.
Thanks a lot! I didn't know if containerd and docker use different local storage.
My containerd local storage didn't have that image, so it wasn't being pushed.
But I couldn't change the tag with ctr command, so I used the docker client.
Is there any way to change the ctr image tag?
Hi @bluefriday . I think you are using v1.2.x containerd version. You use containerd v1.3.x or master, which provides tag functionality.
root@ubuntu-xenial ~/g/s/g/c/containerd# bin/ctr image -h 2d8cc405
NAME:
ctr images - manage images
USAGE:
ctr images command [command options] [arguments...]
COMMANDS:
check check that an image has all content available locally
export export images
import import images
list, ls list images known to containerd
pull pull an image from a remote
push push an image to a remote
remove, rm remove one or more images by reference
tag tag an image <================================== here
label set and clear labels for an image
OPTIONS:
--help, -h show help
Great. Thanks for your reply for me.
I'll close this issue.
Most helpful comment
Great. Thanks for your reply for me.
I'll close this issue.