Podman: Docker image to be used to play with buildah

Created on 17 Jul 2018  Â·  19Comments  Â·  Source: containers/podman

Is there a Docker image that we could use to play with Buildah on non Linux's machine such as Macos ?

Most helpful comment

Podman or buildah will not work natively on a MAC. We need a different client that @jwhonce is working on to run pypodman, a python version of podman which talks over ssh to a VM running podman listening on a varlink socket. This should allow us to run any podman command from a MAC on the VM. (That is the goal.) We are always looking for contributors, especially with MAC experience (Windows Experience also).

All 19 comments

@ipbabble do you know of one that @cmoulliard could play with?

@cmoulliard try this one:
docker pull quay.io/ipbabble/buildah

Would be so much better if this was podman pull :^)

:-) He specifically asked for Docker on a Mac. But I agree.

Action items ?

  1. Port Podman to Mac OS X
  2. Ask Quay to give copy options when using the UI.

-William

On Wed, Jul 18, 2018 at 8:28 AM Daniel J Walsh notifications@github.com
wrote:

Would be so much better if this was podman pull :^)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/projectatomic/buildah/issues/866#issuecomment-405950592,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPpgb2srDFHd9uA9dUNDSLYcZF4g_Uvks5uH0X9gaJpZM4VTByC
.

>

Sent from Gmail Mobile on iPhone

Podman or buildah will not work natively on a MAC. We need a different client that @jwhonce is working on to run pypodman, a python version of podman which talks over ssh to a VM running podman listening on a varlink socket. This should allow us to run any podman command from a MAC on the VM. (That is the goal.) We are always looking for contributors, especially with MAC experience (Windows Experience also).

MAC

Many thanks for the feedback.

If I would like to develop a go application able to build a docker image from a dockerfile + code to be packaged (= a java jar file), is it something that we could achieve easily with a lightweight docker image packaging this "small go app for building/pushing images" ? What are the minimum requirements that I need to build such app and Linux's packages to run it ?

For that you would only need podman package. No buildah required.

podman package

You mean the yum package ?

@cmoulliard yes, I believe @rhatdan meant the yum/dnf package for podman. Do you still have outstanding questions on this or can we close this issue?

Yes the yum podman rpm.

@jwhonce PTAL

I have added support for both podman and buildah to the "minikube" distribution of Kubernetes :

https://github.com/kubernetes/minikube/pull/3225

$ minikube ssh -- sudo podman --version
podman version 0.9.3
$ minikube ssh -- sudo buildah --version
buildah version 1.4 (image-spec 1.0.0, runtime-spec 1.0.0)

So far there is no _real_ replacement for minikube docker-env, except for using minikube ssh :

https://kubernetes.io/docs/setup/minikube/#reusing-the-docker-daemon

We do compile with varlink, so I guess that could be an alternative to "minikube ssh sudo podman" ?
Alternative we could use "kubectl run", by mounting /var/lib/containers into the pod perhaps.

This all assumes that the users have some means of getting files from their environment to the VM...
The support for mounts varies greatly between the drivers, with some using things like vboxsf or 9p.

i.e. there is still no support for the docker "build context" and .dockerignore

The minikube.iso is around 200M, not sure if that qualifies as "light-weight" ?
boot2docker.iso is 40M, so maybe a "boot2containers.iso" is needed here...


The above solution boots to Kubernetes, which might be overkill for this.
But it is using CRI-O for the container runtime, so no Docker is needed.

# systemctl is-active docker
inactive
# systemctl is-active crio
active

PS. Small is just in the eye of the beholder, I suppose ? (300M > 200M)

# sudo podman pull quay.io/ipbabble/buildah
Trying to pull quay.io/ipbabble/buildah...Getting image source signatures
Copying blob sha256:513b2e80e19ce6eff01ce76da64c5bdc3eaedd6ba5f8989d774197f09e4409ef
 301.06 MB / 301.06 MB [===================================================] 36s
Writing manifest to image destination
Storing signatures
84b8f34a3ca8713efb775b22340b2a89d8b60fef9d6dd6acac559d34a8167bdc

Hi Anders,

I will update that version of Buildah. I think it’s old and I should
probably maintain it more often.

Having said that I would like to see a repo on Quay that has Podman and
buildah images kept up to date as part of the CI/CD process.

Maybe we can add some sort of cri -o test as part of the CI process.

William

On Sun, Oct 7, 2018 at 2:58 AM Anders Björklund notifications@github.com
wrote:

I have added support for both podman and buildah to the "minikube"
distribution of Kubernetes :

kubernetes/minikube#3225
https://github.com/kubernetes/minikube/pull/3225

$ minikube ssh -- sudo podman --versionpodman version 0.9.3
$ minikube ssh -- sudo buildah --versionbuildah version 1.4 (image-spec 1.0.0, runtime-spec 1.0.0)

So far there is no real replacement for minikube docker-env, except for
using minikube ssh :

https://kubernetes.io/docs/setup/minikube/#reusing-the-docker-daemon

We do compile with varlink, so I guess that could be an alternative to
"minikube ssh sudo podman" ?
Alternative we could use "kubectl run", by mounting /var/lib/containers
into the pod perhaps.

This all assumes that the users have some means of getting files from
their environment to the VM...
The support for mounts varies greatly between the drivers, with some using
things like vboxsf or 9p.

i.e. there is still no support for the docker "build context
https://docs.docker.com/engine/reference/builder/" and .dockerignore

The minikube.iso is around 200M, not sure if that qualifies as
"light-weight" ?
boot2docker.iso https://github.com/boot2docker/boot2docker is 40M, so

maybe a "boot2containers.iso" is needed here...

The above solution boots to Kubernetes, which might be overkill for this.
But it is using CRI-O for the container runtime
https://github.com/kubernetes/minikube/blob/master/docs/alternative_runtimes.md#using-cri-o,
so no Docker is needed.

systemctl is-active docker

inactive

systemctl is-active crio

active

PS. Small is just in the eye of the beholder, I suppose ? (300M > 200M)

sudo podman pull quay.io/ipbabble/buildahTrying to pull quay.io/ipbabble/buildah...Getting image source signaturesCopying blob sha256:513b2e80e19ce6eff01ce76da64c5bdc3eaedd6ba5f8989d774197f09e4409ef 301.06 MB / 301.06 MB [===================================================] 36sWriting manifest to image destinationStoring signatures84b8f34a3ca8713efb775b22340b2a89d8b60fef9d6dd6acac559d34a8167bdc

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/containers/buildah/issues/866#issuecomment-427637058,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPpgdnX3i_qR8uF0kGcB5y2-2w0d-Toks5uicIbgaJpZM4VTByC
.

>

Sent from Gmail Mobile on iPhone

The "boot2containers.iso" idea is now alive and well, in the boot2podman project.
It turned to be 80M (rather than 40M), but ISO also includes varlink and buildah...

tc@box:~$ sudo podman version
Version:       0.10.2-dev
Go Version:    go1.10.4
OS/Arch:       linux/amd64
tc@box:~$ sudo buildah version
Version:         1.5-dev
Go Version:      go1.10.4
Image Spec:      1.0.0
Runtime Spec:    1.0.0
CNI Spec:        0.4.0
libcni Version:  v0.7.0-alpha1
Git Commit:      d6b7e338
Built:           Sun Oct 28 09:45:34 2018
OS/Arch:         linux/amd64

This is a virtual machine, and not a container image. But it _should_ work on any host ?
Another option is to use pypodman on the host, talking to podman over ssh root@box.

@cmoulliard @ipbabble are we all set with this issue? Can I close it?

I’m good but I haven’t had a chance to follow it for a few weeks. I’ll have
some more time to play with things over Xmas.

William

On Sat, Dec 22, 2018 at 6:11 AM Daniel J Walsh notifications@github.com
wrote:

@cmoulliard https://github.com/cmoulliard @ipbabble
https://github.com/ipbabble are we all set with this issue? Can I close
it?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/containers/libpod/issues/1883#issuecomment-449569163,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPpgXisFZoXcbEygRDzIwwQoGTOH-Fyks5u7i-bgaJpZM4Y2K8t
.

>

Sent from Gmail Mobile on iPhone

where do we stand with this? OSX folks, please give the remote client a try ...

Closing the issue.

Was this page helpful?
0 / 5 - 0 ratings