-
Notifications
You must be signed in to change notification settings - Fork 766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
buildah mount locations not visible to the host #1814
Comments
This definitely looks like a bug. @TomSweeneyRedHat PTAL |
So the volumes are only getting mounted during a RUN or Build. The issue is we rely on the OCI runtime to actually create the content and mount the bind mounts. |
@rhatdan is there something we can do with this? I'm not sure this is unexpected for the mount command as it's used in the example. |
Yes I think we need to close this since we really can not fix this is a reasonable way other then to tell user to run the container As soon as you do a |
We could document this though. |
I will close this out in favor of #1821 , as I guess we are talking about the same thing or the underlying issue is one and the same, and #1821 has more context. Thanks! |
Description
Steps to reproduce the issue:
Get into quay.io/builda container, with a mount:
docker run --privileged -it -v /a:/b -v containers:/var/lib/containers quay.io/buildah/stable /bin/sh
Create something under the mount
echo hello > /b/foo.txt
Create a container from scratch, with the mount forwarding to the child
buildah from --name cont -v /b:/c scratch
Get the mount point of the chile
mount=``buildah mount cont
`Check the content of the mount point:
ls -lrt $mount/
Describe the results you received:
I got
total 0
Describe the results you expected:
I expected:
-rw-r--r-- 1 root root 6 Aug 22 13:56 foo.txt
or similarOutput of
rpm -q buildah
orapt list buildah
:I have tried several mount options such as
:shared
etc. but did not succeed.If I run
buildah run
on the container and get in, I can see the mount points properly - which indicates the mount, and its access permissions, visibility and share-ability are all good.Output of
buildah version
:Output of
podman version
if reporting apodman build
issue:Output of
cat /etc/*release
:Output of
uname -a
:Output of
cat /etc/containers/storage.conf
:Thanks in advance!
The text was updated successfully, but these errors were encountered: