Closed Miaoxiang-philips closed 3 months ago
Hey @Miaoxiang-philips, it looks like you accidentally used hauler store pull my_image:tag
, when it should be hauler store add image my_image:tag
.
You are able to docker push
to the registry, but we don't recommend it, because artifacts won't be added to the store
. It might be useful to check out the quickstart guide! --> https://rancherfederal.github.io/hauler-docs/docs/introduction/quickstart
You are able to
docker push
to the registry, but we don't recommend it, because artifacts won't be added to thestore
.
We have no plans at this time to support collecting images into the store via push.
Hey Team !
We used
hauler store serve registry
to start my image registry onA
And then, We need to upload image externally to this registry,
So we do it:
B
, Runhauler store pull my_image:tag
hauler store copy registry://target_hauler_registry_server:port
it works, but when i use
hauler store info
onA
, i can't find my uploaded image, but it can usedocker pull A_IP:port/my_image:tag
to pull imageI'm not sure if this conflicts with the goal of hauler. My understanding is that since it is possible to upload(hauler copy) images, it should provide a view of the list of all images
Describe Proposed Solution(s):
Describe Possible Alternatives:
registry/
metadata information, But it's not friendlyAdditional Context:
-