It appears that the directory could not be mounted. #5309
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
stale-issue
Comments
openshift-ci-robot
added
the
kind/bug
|
@TomSweeneyRedHat PTAL - looks like a build issue |
|
@daiaji can you verify that I'm using the right Dockerfile? It seems to be working for me as a rootless user and as root. |
|
@TomSweeneyRedHat In fact, I can't even run the container. Is this related to the subuid and subgid settings? |
|
Can you provide the full output of |
|
|
@daiaji just double checking were you logged on as the 'fake' user when you did the run? Are you able to run this as root? |
|
@TomSweeneyRedHat I just replaced the user name in the log. In fact, I am using another user name, which can work under root. |
|
Error's definitely out of runc, but I'm not exactly sure what it is. Manpages say that mount(2) can't return EEXIST so this is probably some form of check before the mount is made? |
|
This is our relevant code block: I'm betting the cause is that initial Lstat |
|
Hmm. Actually, probably not. Could be the MkdirAll. |
|
@daiaji Any chance the |
|
@mheon Fortunately, although the official software source does not have crun, I found the community maintenance package. Unfortunately, the community software source does not provide the binary package of i586, but the spec template file can be compiled on the i586 architecture. Just a year ago, I compiled one or two packages. After splitting the spec template file and compiling it, I still got the package on the i586 architecture. |
|
@giuseppe Any thoughts here? |
|
Could be the interaction runc with fuse-overlays, I'll need to check. Also it can be the 32 bits arch, I have never tried fuse-overlays there |
|
just to make sure the namespace is created correctly, could you show the output for |
|
|
it seems you are running it in the host. Please use
|
|
|
the userns looks good. At this point, I am afraid it depends from the arch you are using |
|
@giuseppe I will try to test podman on the new 32bit openSUSE or switch to 32bit Ubuntu test. |
|
A friendly reminder that this issue had no activity for 30 days. |
|
@daiaji I take it this is fixed, or works for you. |
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue:
1.Compiling image for non root users
Describe the results you received:
podman build -t v2ray .
STEP 1: FROM alpine AS builder
STEP 2: RUN apk update && apk add --no-cache bash ca-certificates curl unzip && curl $CURLPROXY -fsSL https://install.direct/go.sh | bash -s -- $V2RAYPROXY && curl $CURLPROXY -fsSLo /usr/bin/v2ray/h2y.dat https://raw.githubusercontent.com/ToutyRater/V2Ray-SiteDAT/master/geofiles/h2y.dat
WARN[0000] signal: killed
ERRO[0000] container_linux.go:349: starting container process caused "process_linux.go:449: container init caused "rootfs_linux.go:58: mounting \"/dev\" to rootfs \"/var/tmp/buildah335681964/mnt/rootfs\" at \"/dev\" caused \"mkdir /var/tmp/buildah335681964/mnt/rootfs/dev: file exists\"""
container_linux.go:349: starting container process caused "process_linux.go:449: container init caused "rootfs_linux.go:58: mounting \"/dev\" to rootfs \"/var/tmp/buildah335681964/mnt/rootfs\" at \"/dev\" caused \"mkdir /var/tmp/buildah335681964/mnt/rootfs/dev: file exists\"""
error running container: error creating container for [/bin/sh -c apk update && apk add --no-cache bash ca-certificates curl unzip && curl $CURLPROXY -fsSL https://install.direct/go.sh | bash -s -- $V2RAYPROXY && curl $CURLPROXY -fsSLo /usr/bin/v2ray/h2y.dat https://raw.githubusercontent.com/ToutyRater/V2Ray-SiteDAT/master/geofiles/h2y.dat]: : exit status 1
Error: error building at STEP "RUN apk update && apk add --no-cache bash ca-certificates curl unzip && curl $CURLPROXY -fsSL https://install.direct/go.sh | bash -s -- $V2RAYPROXY && curl $CURLPROXY -fsSLo /usr/bin/v2ray/h2y.dat https://raw.githubusercontent.com/ToutyRater/V2Ray-SiteDAT/master/geofiles/h2y.dat": error while running runtime: exit status 1
Describe the results you expected:
Successfully compiled the image without root.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version:Output of
podman info --debug:Package info (e.g. output of
rpm -q podmanorapt list podman):Additional environment details (AWS, VirtualBox, physical, etc.):
This doesn't happen when I use root
The text was updated successfully, but these errors were encountered: