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
When a user makes use of an image source, they should be able to run commands in the context of that base image, including being able to rely on the presence of files under arbitrary subpaths
Actual Behavior
If a user specifies a non-root subpath to extract from the base image then we mount a scratch fs over said path without accounting for what might have been at that path, meaning that commands meant to execute in the context of the base image may fail and files from the base image under a particular subpath that were meant to be persisted when the subpath contents are extracted will not be copied as part of the source.
The contents of /etc from busybox should be available under the img source directory, and the test command within the build steps should succeed. Instead, the build fails because there are no files in the img source directory. This is due to faulty current behavior in our source-from-image implementation in which we unconditionally mount a scratch fs over any non-root subpath a user has provided in the base image.
Are you willing to submit PRs to contribute to this bug fix?
Yes, I am willing to implement it.
The text was updated successfully, but these errors were encountered:
Expected Behavior
When a user makes use of an image source, they should be able to run commands in the context of that base image, including being able to rely on the presence of files under arbitrary subpaths
Actual Behavior
If a user specifies a non-root subpath to extract from the base image then we mount a scratch fs over said path without accounting for what might have been at that path, meaning that commands meant to execute in the context of the base image may fail and files from the base image under a particular subpath that were meant to be persisted when the subpath contents are extracted will not be copied as part of the source.
Steps To Reproduce
Consider the following spec:
The contents of
/etc
frombusybox
should be available under theimg
source directory, and the test command within the build steps should succeed. Instead, the build fails because there are no files in theimg
source directory. This is due to faulty current behavior in our source-from-image implementation in which we unconditionally mount a scratch fs over any non-root subpath a user has provided in the base image.Are you willing to submit PRs to contribute to this bug fix?
The text was updated successfully, but these errors were encountered: