You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to understand the root cause of the following issue with the amazonlinux:2 docker image. Whenever I run cp inside of a running container the command behaves differently depending on the mount-type filesystem specified. Please check the repo-steps below where I was trying to run cp -au . dst-dir in 3 different scenarios. The first one was unexpectedly failing with No data available, while the other two were working as expected, in all test-cases the cp command was the same.
Version
colima version 0.7.3
git commit: a66b375e8df84ff2860797efc683e66632bcbce3
limactl version 0.23.1
qemu-img version 9.0.2
Operating System
macOS Intel <= 13 (Ventura)
macOS Intel >= 14 (Sonoma)
Apple Silicon <= 13 (Ventura)
Apple Silicon >= 14 (Sonoma)
Linux
Output of colima status
Please check the repro-steps below.
Reproduction Steps
Prepare a sample directory structure:
$ mkdir test ; cd test
$ mkdir src ; mkdir result
$ echo 'empty file' | tee ./src/dummy
Check a negative test-case scenario (expected - success, received - failure):
Description
hello,
I am trying to understand the root cause of the following issue with the
amazonlinux:2
docker image. Whenever I runcp
inside of a running container the command behaves differently depending on the mount-type filesystem specified. Please check the repo-steps below where I was trying to runcp -au . dst-dir
in 3 different scenarios. The first one was unexpectedly failing withNo data available
, while the other two were working as expected, in all test-cases thecp
command was the same.Version
Operating System
Output of
colima status
Please check the repro-steps below.
Reproduction Steps
Prepare a sample directory structure:
Check a negative test-case scenario (expected - success, received - failure):
Check a positive test-case scenario (vz, expected - success, received - success):
Check a positive test-case scenario (rosetta, expected - success, received - success):
Expected behaviour
I would like to understand what's wrong with the
virtiofs
file-system, and make sure thatcp
command works as expected.Additional context
if I try colima
0.5.6
, it doesn't have this issueThe text was updated successfully, but these errors were encountered: