-
Notifications
You must be signed in to change notification settings - Fork 309
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
dockerignore with globs creates empty folders #6393
Labels
bug
Something isn't working
Comments
...also to mention: |
thanks for the report! ya, i can repro |
ah, i remember this, this is related to docker/compose#11426. if you don't create the empty directory, buildkit explodes. we have to unwind some vendor deps to get the fix, and then we can remove the dir. |
nicks
added a commit
to nicks/fsutil
that referenced
this issue
Jun 26, 2024
if the Map() function excludes a directory, but includes a file inside that directory, then the walker must backtrack and include the directory. otherwise, buildkit gets confused and sends "changes out of order" errors. part of fixing tilt-dev/tilt#6393 Signed-off-by: Nick Santos <[email protected]>
nicks
added a commit
to nicks/fsutil
that referenced
this issue
Jul 2, 2024
if the Map() function excludes a directory, but includes a file inside that directory, then the walker must backtrack and include the directory. otherwise, buildkit gets confused and sends "changes out of order" errors. part of fixing tilt-dev/tilt#6393 Signed-off-by: Nick Santos <[email protected]>
nicks
added a commit
to nicks/fsutil
that referenced
this issue
Jul 2, 2024
if the Map() function excludes a directory, but includes a file inside that directory, then the walker must backtrack and include the directory. otherwise, buildkit gets confused and sends "changes out of order" errors. part of fixing tilt-dev/tilt#6393 Signed-off-by: Nick Santos <[email protected]>
nicks
added a commit
to nicks/fsutil
that referenced
this issue
Jul 3, 2024
if the Map() function excludes a directory, but includes a file inside that directory, then the walker must backtrack and include the directory. otherwise, buildkit gets confused and sends "changes out of order" errors. part of fixing tilt-dev/tilt#6393 Signed-off-by: Nick Santos <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
Tilt should behave same as docker when using
.dockerignore
files. In particular it should be able to use the**
pattern to ignore all files and directories but allow the!
pattern to include specific files.Current Behavior
When using the
**
pattern of.dockerignore
to exclude everything, including a folder containing some files, in combination with the!
pattern to include some files using a glob (*
), the folder is not ignored but created without containing files.i.e.
Steps to Reproduce
tilt up
ls -al
Context
tilt doctor
OutputAbout Your Use Case
We were facing this issue when Tilt was copying a local python virtualenv folder to the image containing empty site-package folders which led to failures starting the python project.
The text was updated successfully, but these errors were encountered: