profile
viewpoint
William Henry ipbabble @projectatomic Red Hat Colorado, USA Senior Distinguished Engineer at Red Hat. 30 years in the software industry.

issue commentcontainers/libpod

Podman tutorial lacks rootless setup instructions

"Cobbled"? "Cobbled"? I'll have you know I don't cobble my demos! There was painstaking research and testing involved! ;-) LOL

FYI I have started looking at this myself and hit errors on using $ podman images on fedora 31.
$ sudo podman images worked fine. I have subuid and subgid files. in /etc/

So we need to just say what needs to be done to get this working (it worked on fedora 30. I wonder if I need to rm /etc/subuid /etc/subgid ?

mheon

comment created time in 21 days

issue commentcontainers/libpod

Podman tutorial lacks rootless setup instructions

Who wrote the original tutorial btw?

mheon

comment created time in 21 days

issue commentcontainers/buildah

"Buildah Tutorial 1" should emphasize what needs to be run as root

This is strange. Can you tell us more about this buildah/stable:v1.11.2 ?

I assume you are pulling it down with Docker before trying to run it, right? (just checking to eliminate some obvious gotchas)

I promised to work on the other issues but failed to do so because of travel. I will spend time on this today.

-ipbabble

On Wed, Oct 2, 2019 at 8:28 AM ITChap notifications@github.com wrote:

New user here. I have spent the pass 2 days trying to get my head around running buildah in my kubernetes cluster. As mentioned https://developers.redhat.com/blog/2019/08/14/best-practices-for-running-buildah-in-a-container/ is very useful but it was pretty surprising to be able to run quay.io/buildah/stable:v1.11.2 on my kubernetes cluster but not locally on docker.

I had and still have issues with the basic build and push in a container and if interested I can open a different issue to describe which part of the doc is lacking.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/containers/buildah/issues/1469?email_source=notifications&email_token=AAJ6TALB3ZSI47JSOIC324LQMSVXTA5CNFSM4HDHCHM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAE6GQA#issuecomment-537518912, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJ6TAO3FS5ZVX4FXFVW76TQMSVXTANCNFSM4HDHCHMQ .

--

William G Henry

Senior Distinguished Engineer

Red Hat https://www.redhat.com

M: +17192716951 IM: ipbabble https://www.redhat.com

rpjday

comment created time in 2 months

fork ipbabble/skupper-cli

Command line tool for setting up and managing skupper installations

fork in 2 months

fork ipbabble/kqr-pay

Sample QR app for Knative

fork in 3 months

fork ipbabble/client

Knative developer experience, docs, reference Knative CLI implementation

fork in 3 months

issue commentcontainers/buildah

"Buildah Tutorial 1" should emphasize what needs to be run as root

I will do my best to look at this tomorrow - Thurs.

-William

William G Henry

Senior Distinguished Engineer

Red Hat https://www.redhat.com

M: +17192716951 IM: ipbabble https://www.redhat.com

On Wed, Aug 21, 2019 at 4:25 AM Pascal Bach notifications@github.com wrote:

@ipbabble https://github.com/ipbabble I don't think that has anything to do with the Dockerfile.

I tried with a minimal Dockerfile:

FROM alpine:latest

If I run buildah inside a privileged container docker run --rm -it -v "$(pwd):/build:rw" --privileged quay.io/buildah/stable everything works as expected:

$ buildah bud /build STEP 1: FROM alpine:latest Getting image source signatures Copying blob 9d48c3bd43c5 done Copying config 9617696764 done Writing manifest to image destination Storing signatures STEP 2: COMMIT 961769676411f082461f9ef46626dd7a2d1e2b2a38e6a44364bcbecf51e66dd4

If I run it inside a unprivileged container docker run --rm -it -v "$(pwd):/build:rw" quay.io/buildah/stable it get the same error as @t3hmrman https://github.com/t3hmrman :

$ buildah bud /build Error during unshare(CLONE_NEWUSER): Operation not permitted ERRO[0000] error parsing PID "": strconv.Atoi: parsing "": invalid syntax ERRO[0000] (unable to determine exit status)

Note that I have already setup sysctl -w kernel.unprivileged_userns_clone=1

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/containers/buildah/issues/1469?email_source=notifications&email_token=AAJ6TAOL3WIRFJJ3GZ7KFSDQFUJ2DA5CNFSM4HDHCHM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4ZGPWI#issuecomment-523397081, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJ6TAPVTGPFWMIAUDEIX4LQFUJ2DANCNFSM4HDHCHMQ .

rpjday

comment created time in 3 months

more