-
Notifications
You must be signed in to change notification settings - Fork 18.7k
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
integration-cli: update TestCreateWithWorkdir for Hyper-V isolation #39876
Conversation
@StefanScherer @vikramhh ptal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible that on some [slow or heavily loaded] machines, the container may not stop in time for the next check in line 321?
# container runs a shell to mimic a slow stopping container (will ignore SIGTERM, and be SIGKILL'd after 10 seconds)
docker run -dit --rm --name foobar busybox
# time how long it takes to stop; you can see it waits for 10 seconds+
time -p docker stop foobar
real 10.67
user 0.03
sys 0.01 |
This is funny because I believe we use |
Looks like we have a flakey unit test:
|
And one on Windows, unrelated:
|
bb39cd5
to
b83c505
Compare
Hyper-V isolated containers do not allow file-operations on a running container. This test currently uses `docker cp` to verify that the WORKDIR was automatically created, which cannot be done while the container is running. ``` FAIL: docker_cli_create_test.go:302: DockerSuite.TestCreateWithWorkdir assertion failed: Command: d:\CI-7\CI-f3768a669\binary\docker.exe cp foo:c:\home\foo\bar c:\tmp ExitCode: 1 Error: exit status 1 Stdout: Stderr: Error response from daemon: filesystem operations against a running Hyper-V container are not supported Failures: ExitCode was 1 expected 0 Expected no error ``` Signed-off-by: Sebastiaan van Stijn <[email protected]>
b83c505
to
ac9ef84
Compare
@cpuguy83 updated; ptal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
(taken from #39846)
Hyper-V isolated containers do not allow file-operations on a running container. This test currently uses
docker cp
to verify that the WORKDIR was automatically created, which cannot be done while the container is running.