Skip to content
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

Don't remove empty directories after build. #1405

Merged

Conversation

larskanis
Copy link
Member

Deletion of these empty directories is flawed on docker with overlayfs, so we better avoid it. The build artifacts are still removed after gem install.

This fixes nokogiri issue #1370 . For further details to the root issue see: moby/moby#19082

Deletion of these empty directories is flawed on docker with overlayfs,
so we better avoid it.
The build artifacts are still removed after gem install.

This fixes nokogiri issue sparklemotion#1370 .
For further details to the root issue see: moby/moby#19082
larskanis added a commit that referenced this pull request Jan 6, 2016
…layfs

Don't remove empty directories after build.
@larskanis larskanis merged commit f5a9dc9 into sparklemotion:master Jan 6, 2016
@flavorjones
Copy link
Member

Thanks for tracking this down.

@flavorjones flavorjones added this to the 1.6.8 milestone Jan 11, 2016
@shinnn
Copy link

shinnn commented Apr 1, 2016

@flavorjones Would you consider publishing v1.6.7.3 that includes this change? It's really helpful for the developers using Docker-based CI services (e.g. wercker).

@DeviaVir
Copy link

@flavorjones echo-ing what @shinnn asked, we're running docker in production and keep getting bitten by this bug, our workaround to downgrade rubygems for just nokogiri is no longer viable due to other deps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants