On 2/21/22 16:58, Hendrik Haddorp wrote:
Isn't "podman build" using the Dockerfile directly? I
don't want to
build directly using a Dockerfile but using the docker network API, as
that is what all other tools use.
Podman --remote build uses the Podman API and supports the Dockerfile
and Containerfile format.
Podman build uses Dockerfile and Containerfile format locally.
On 2/21/22 22:15, Daniel Walsh wrote:
> On 2/21/22 11:00, Hendrik Haddorp wrote:
>> Hi Matt,
>>
>> I would like "podman system service" to run in qemu so that I can
>> use the a Dockerbuild, via docker network API. For example start the
>> podman system service in qemu mode and then build a docker container
>> using a gradle base build
>> (
https://github.com/bmuschko/gradle-docker-plugin). This would
>> communicate to podman via the unix domain socket.
>>
> You should be able to do this with
>
> podman --connection build ...
>
>
> And point the connection at different VMs/Systems running for
> different Arches.
>
>> regards,
>> Hendrik
>>
>>
>> On 2/21/22 15:42, Matt Heon wrote:
>>> To be a bit more clear about what you're asking for - do you want
>>> to run every container/pod as a given architecture, or more
>>> specifically to run `podman system service` itself inside of QEMU?
>>>
>>> The former sounds like a not-too-difficult feature request we could
>>> handle via `containers.conf`; the latter seems a bit more involved.
>>>
>>> Thanks,
>>> Matt Heon
>>>
>>> On Fri, Feb 18, 2022 at 2:03 AM Hendrik Haddorp
>>> <hendrik.haddorp(a)gmx.net> wrote:
>>>
>>> Hi,
>>>
>>> using "podman run --arch ..." it's quite easy to start
>>> containers for a
>>> different architecture with the support of qemu. "podman system
>>> service"
>>> does however not seem to have the same support. I would like to
>>> use a
>>> docker build from existing tooling for a different
>>> architecture. So this
>>> would use the docker API that the podman system service provides. I
>>> guess it should be possible to start a container using podman
>>> run --arch
>>> an then start the podman system service in there. Is there a
>>> simpler way
>>> as podman in podman has quite often some setup issues and the whole
>>> handling would be more complicated?
>>>
>>> thanks,
>>> Hendrik
>>> _______________________________________________
>>> Podman mailing list -- podman(a)lists.podman.io
>>> To unsubscribe send an email to podman-leave(a)lists.podman.io
>>>
>>>
>>> _______________________________________________
>>> Podman mailing list --podman(a)lists.podman.io
>>> To unsubscribe send an email topodman-leave(a)lists.podman.io
>>
>>
>> _______________________________________________
>> Podman mailing list --podman(a)lists.podman.io
>> To unsubscribe send an email topodman-leave(a)lists.podman.io
>
>
>
> _______________________________________________
> Podman mailing list --podman(a)lists.podman.io
> To unsubscribe send an email topodman-leave(a)lists.podman.io
_______________________________________________
Podman mailing list --podman(a)lists.podman.io
To unsubscribe send an email topodman-leave(a)lists.podman.io