-
Notifications
You must be signed in to change notification settings - Fork 96
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
Container build still crashes on apt-get issue #452
Comments
Could we use Structure of mounted cache:
Possibly it is worth to make the feature optional as it may require extended attributes for opaque directories (although in our case |
Also maybe it would be better to place As a drawback we need somehow to clean those directories if build fails. |
Yes sounds good (I think overlayfs didn't work in unprivileged mode in 2017 when issue was created :) ). And I think it's fine to put upper dir in container's directory (somewhere below root). I think it's common enough to put cache and container directories into the same volume (and by default vagga puts everything into the project dir anyways).
Can we detect whether this works, rather than requiring user to set the option manually? We can probably try mount and write (delete?) file. So we check both: whether unprivileged unionfs works and extended attributes. |
The crashed process:
The waiting process:
Probably the problem is because the first one has PPAs enabled and they might be cleaned on clean install of the second container (as you might note, it's installing the
locales
package, which means it's the firstUbuntu
step)Probably our lock doesn't help with this :(
/cc @anti-social
The text was updated successfully, but these errors were encountered: