We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It's going to take the fix in containers/bootc#485 a while to propagate so here's a terrible hack that comes to mind:
We can create a wrapper shell script for losetup that just ignores the --direct-io=on argument and bind mount that in when running the container.
losetup
--direct-io=on
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
It's going to take the fix in containers/bootc#485 a while to propagate so here's a terrible hack that comes to mind:
We can create a wrapper shell script for
losetupthat just ignores the--direct-io=onargument and bind mount that in when running the container.The text was updated successfully, but these errors were encountered: