I have done the following
Steps to reproduce
There is a problem in the virtualization framework where files with more than one hard link may not be accessible when mounted via virtiofs into a VM.
The problem would affect any such files in a virtiofs share, but it is particularly evident with our single-file mount method, where we create an isolated mount source directory on the host and create a link to the source file in that directory.
echo "Hello, world!" > hello.txt
container run -it --rm -v ${PWD}/hello.txt:/hello.txt alpine sh
cat hello.txt
Current behavior
Sometimes we see the expected behavior, but other times it's:
% container run -it --rm -v ${PWD}/hello.txt:/hello.txt alpine sh
Warning! Running debug build. Performance may be degraded.
/ # vi hello.txt
/ # cat hello.txt
cat: can't open 'hello.txt': Permission denied
/ #
Expected behavior
% container run -it --rm -v ${PWD}/hello.txt:/hello.txt alpine sh
Warning! Running debug build. Performance may be degraded.
/ # cat hello.txt
Hello, world!
/ #
Environment
- OS: 26
- Xcode: 26
- Container: main
Relevant log output
Code of Conduct
I have done the following
Steps to reproduce
There is a problem in the virtualization framework where files with more than one hard link may not be accessible when mounted via virtiofs into a VM.
The problem would affect any such files in a virtiofs share, but it is particularly evident with our single-file mount method, where we create an isolated mount source directory on the host and create a link to the source file in that directory.
Current behavior
Sometimes we see the expected behavior, but other times it's:
Expected behavior
Environment
Relevant log output
Code of Conduct