On 8/6/19 9:15 AM, Jun Aruga wrote:
>>> Please come!
>>>
>> Would love to see your examples use podman...
> Sorry here is the podman's example.
> And no worry. podman's examples are used as much as possible in my talk!
>
> ```
> $ uname -m
> x86_64
>
> $ podman run --rm -t arm64v8/fedora:30 uname
> > Please come!
> >
> Would love to see your examples use podman...
Sorry here is the podman's example.
And no worry. podman's examples are used as much as possible in my talk!
```
$ uname -m
x86_64
$ podman run --rm -t arm64v8/fedora:30 uname -m
standard_init_linux.go:211: exec user process
On 8/6/19 7:56 AM, Jun Aruga wrote:
>> ```
>> $ docker run --rm -t arm64v8/fedora:30 uname -m
> standard_init_linux.go:207: exec user process caused "no such file or
> directory"
>> $ docker run --rm --privileged multiarch/qemu-user-static:register --reset
>> $ docker run --rm -t
> ```
> $ docker run --rm -t arm64v8/fedora:30 uname -m
standard_init_linux.go:207: exec user process caused "no such file or directory"
>
> $ docker run --rm --privileged multiarch/qemu-user-static:register --reset
> $ docker run --rm -t quay.io/junaruga/multiarch-fedora:30-aarch64 uname -m
>
On 5/19/19 9:11 AM, Jun Aruga wrote:
> I am suggesting a new feature "podman buildx" like "docker buildx"
> that makes a better multi arch build experience.
> See below URL if you are interested in it.
>
> Supporting building multi-platform images (podman buildx)
>
I am suggesting a new feature "podman buildx" like "docker buildx"
that makes a better multi arch build experience.
See below URL if you are interested in it.
Supporting building multi-platform images (podman buildx)
https://github.com/containers/buildah/issues/1590
--
Jun Aruga / He - His -
> > you should just run
> > $ docker run --rm -t fedora:30 uname -m
> > on all arches, we push manifest listed containers to dockerhub so that
> > command will work everywhere.
>
> Alright, I did not know the kind of alias feature. Thanks for the info.
But my motivation is not like
* Running
> > ```
> > $ docker run --rm -t arm64v8/fedora:30 uname -m
> > standard_init_linux.go:207: exec user process caused "no such file or
> > directory"
> > ```
>
> you should just run
> $ docker run --rm -t fedora:30 uname -m
> on all arches, we push manifest listed containers to dockerhub so that
>
On Thu, May 9, 2019 at 10:22 AM Jun Aruga wrote:
>
> Kevin and Clement, thanks for the explanation.
>
> I am looking forward to seeing the final compose.
>
> > So, likely we haven't had a armv7 fedora 30 compose recently, and so no
> one has updated it. The container sig would be the ones to ask
Kevin and Clement, thanks for the explanation.
I am looking forward to seeing the final compose.
> So, likely we haven't had a armv7 fedora 30 compose recently, and so no
one has updated it. The container sig would be the ones to ask here.
Sure, I will subscribe the mailing list.
> Yes I do
On Tue, 7 May 2019 at 23:46, Kevin Fenzi wrote:
>
> On 5/6/19 11:57 AM, Jun Aruga wrote:
> > Yes, Kevin. Thank you for the info.
> > What I do not understand is below DockerHub has Feodra 30 ppc64le,
> > Fedora 29 armhfp that Fedora Project did not release.
> >
> >
On 5/6/19 11:57 AM, Jun Aruga wrote:
> Yes, Kevin. Thank you for the info.
> What I do not understand is below DockerHub has Feodra 30 ppc64le,
> Fedora 29 armhfp that Fedora Project did not release.
>
> https://hub.docker.com/r/ppc64le/fedora/
> Fedora 29, 30
>
> pungi is the tool, and this:
> https://pagure.io/pungi-fedora/blob/f30/f/fedora-final.conf
> was the config used.
Kevin, I have a question.
https://pagure.io/pungi-fedora/blob/f30/f/fedora-final.conf#_322
> 'arches': ['armhfp', 'aarch64', 'ppc64le', 's390x', 'x86_64'],
From above setting for
> > And why below s390x does not have Fedora-Container-Base-*.tar.xz?
>
> Those are things that failed in the final RC2 compose of Fedora30.
>
> Since they were not release blocking, they... didn't block the release.
>
> ...snip...
> >
> > I change my question.
> > Do you know who is creating this
On 5/6/19 4:58 AM, Jun Aruga wrote:
> I am looking for arch container archive files like
> "Fedora-Container-Base-30-1.2.aarch64.tar.xz
> " for Fedora 30
> I found the x86_64, aarch64 and s390x's archive files in below directory.
> But where is the archive file of armv7hl, i686 and ppc64le?
> I
I found Fedora 30 armhfp container image here.
https://dl.fedoraproject.org/pub/fedora/linux/development/30/Container/
I am still looking for Fedora 30 armv7hl, i686 and ppc64le container images.
--
Jun Aruga / He - His - Him
jar...@redhat.com / IRC: jaruga
I change my question.
Do you know who is creating this kind of multi arch container images?
https://dl.fedoraproject.org/pub/fedora/linux/releases/30/Container/aarch64/images/
Jun
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe
I am looking for arch container archive files like
"Fedora-Container-Base-30-1.2.aarch64.tar.xz
" for Fedora 30.
I found the x86_64, aarch64 and s390x's archive files in below directory.
But where is the archive file of armv7hl, i686 and ppc64le?
I assume the multi archs except x86_64, aarch64 and
18 matches
Mail list logo
