Skip to content
This repository was archived by the owner on Jun 28, 2024. It is now read-only.

integration/docker: unskip docer cp test#971

Merged
grahamwhaley merged 1 commit intokata-containers:masterfrom
devimc:topic/left_mount_points
Jan 23, 2019
Merged

integration/docker: unskip docer cp test#971
grahamwhaley merged 1 commit intokata-containers:masterfrom
devimc:topic/left_mount_points

Conversation

@devimc
Copy link
Copy Markdown

@devimc devimc commented Dec 5, 2018

Unskip docker cp test to check mount points are not left
after running docker cp.

Depends-on: github.com/kata-containers/runtime#980

fixes #970

Signed-off-by: Julio Montes julio.montes@intel.com

@devimc
Copy link
Copy Markdown
Author

devimc commented Dec 5, 2018

/test

@jodh-intel
Copy link
Copy Markdown

jodh-intel commented Dec 6, 2018

lgtm

Approved with PullApprove

@GabyCT
Copy link
Copy Markdown
Contributor

GabyCT commented Dec 10, 2018

lgtm

Approved with PullApprove

@jodh-intel
Copy link
Copy Markdown

Looks like the metrics CI result has been zapped. I can't see how to re-test just this PR under the metrics CI.

/cc @devimc, @grahamwhaley.

@grahamwhaley
Copy link
Copy Markdown
Contributor

yep, that is because the last run was too long ago, and our Jenkins server expires old logs and jobs (I don't remember the rate - it may only keep job history for a week).
I can notionally hand-craft a run if we really want (you have to hand-edit the rebuild info/dialog of another job, it's a little messy hack). Or, we will just have to fire the whole test cycle again - which, given we've not tested since Dec. 5th, is probably the right thing to do to ensure we test with the latest code base... So, here goes...

/test

Unskip docker cp test to check mount points are not left
after running docker cp.

Depends-on: github.com/kata-containers/runtime#980

fixes kata-containers#970

Signed-off-by: Julio Montes <julio.montes@intel.com>
@devimc devimc force-pushed the topic/left_mount_points branch from 41c8d87 to d431cdb Compare January 7, 2019 16:22
devimc pushed a commit to devimc/kata-runtime that referenced this pull request Jan 7, 2019
When overlay is used as storage driver, kata runtime creates a new bind mount
point to the merged directory, that way this directory can be shared with the
VM through 9p. By default the mount propagation is shared, that means mount
events are propagated, but umount events not, to deal with this problem and to
avoid left mount points in the host once container finishes, the mount
propagation of bind mounts should be set to private.

Depends-on: github.com/kata-containers/tests#971

fixes kata-containers#794

Signed-off-by: Julio Montes <julio.montes@intel.com>
@devimc
Copy link
Copy Markdown
Author

devimc commented Jan 7, 2019

/test

devimc pushed a commit to devimc/kata-runtime that referenced this pull request Jan 8, 2019
When overlay is used as storage driver, kata runtime creates a new bind mount
point to the merged directory, that way this directory can be shared with the
VM through 9p. By default the mount propagation is shared, that means mount
events are propagated, but umount events not, to deal with this problem and to
avoid left mount points in the host once container finishes, the mount
propagation of bind mounts should be set to private.

Depends-on: github.com/kata-containers/tests#971

fixes kata-containers#794

Signed-off-by: Julio Montes <julio.montes@intel.com>
@bergwolf
Copy link
Copy Markdown
Member

/test

@jodh-intel
Copy link
Copy Markdown

Ping @devimc - this still has a dnm label - should it have that?

@devimc
Copy link
Copy Markdown
Author

devimc commented Jan 23, 2019

@jodh-intel nop, removing dnm label, thanks

@jodh-intel
Copy link
Copy Markdown

Thanks @devimc. Ping @kata-containers/tests for more reviews.

@grahamwhaley grahamwhaley merged commit e819dc6 into kata-containers:master Jan 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

unskip docker cp "check mount points" test

6 participants