[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [atomic-devel] atomic pull from containers-storage

On Thu, Feb 1, 2018 at 5:16 AM, Chris Negus <cnegus redhat com> wrote:
> ----- Original Message -----
>> HI,
>> there was already a similar request on the list before for which I
>> have a follow-up question.
>> Let's say I have an image created by buildah and the the image has
>> been written to the storage location as defined in
>> /etc/containers/storage.conf. The default is
>> /var/lib/containers/storage. Now I want to pull the image from this
>> storage and store it into an ostree repository using the atomic tool.
>> This does't seem to work.
>> Let's take a look at the buildah default storage:
>> # sudo buildah images
>> IMAGE ID             IMAGE NAME
>>        CREATED AT             SIZE
>> 0e04578ef6b7         docker.io/library/foobar:latest
>>        Jan 28, 2018 09:48     251 MB
>> When I try to pull this image with atomic, it does not work as expected:
>> # sudo atomic pull --storage ostree containers-storage:foobar:latest
>> The image `containers-storage:foobar:latest` is not fully qualified.
>> The default registry configured for Skopeo will be used.
>> FATA[0000] Invalid source name
>> docker://containers-storage:foobar:latest: invalid reference format
>> Is this because atomic does not support the containers-storage
>> transport? What else should I use in order to pull an image from this
>> storage?
> I can't find "containers-storage" referenced in any atomic man pages. There is ostree storage, but I couldn't get that or containers-storage to work as a place to pull from. Maybe someone who knows more that I do could shed some light on this.

Same here. I think that would be a RfE for atomic.

> One thing that did work is to push the image created by buildah to a registry, then use atomic pull. With the docker-distribution service running on the local host, I did this after building an image with buildah named "foobar":
> # buildah push --tls-verify=false foobar:latest localhost:5000/foobar:latest
> # atomic pull --storage ostree http:localhost:5000/foobar
> # atomic images list | grep foobar
>    localhost:5000/foobar   latest   a76583269cbd   2018-01-31 22:04   31.29 MB       ostree

I tried that too. But on a build system where I build images with
buildah to avoid the need to have any docker service installed, I just
want atomic to be able to pull an image out of the storage that is
used by buildah.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]