-
Notifications
You must be signed in to change notification settings - Fork 34
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
misleading errors when running on nfs and overlay #289
Comments
and other ideas for debugability: |
statfs() so b)? |
rchincha
added a commit
to rchincha/stacker
that referenced
this issue
Jul 22, 2023
Add a check for remote-mounted filesystems like NFS. project-stacker#289 Signed-off-by: Ramkumar Chinchani <rchincha@cisco.com>
rchincha
added a commit
to rchincha/stacker
that referenced
this issue
Jul 23, 2023
Add a check for remote-mounted filesystems like NFS. project-stacker#289 Signed-off-by: Ramkumar Chinchani <rchincha@cisco.com>
hallyn
pushed a commit
that referenced
this issue
Jul 29, 2023
Add a check for remote-mounted filesystems like NFS. #289 Signed-off-by: Ramkumar Chinchani <rchincha@cisco.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
overlayfs does not work on nfs. When using stacker, the failure path is quite non-obvious there.
Below is output of stacker current tip on nfs build.
Reasons why I lost time debugging this:
I'd like to suggest that:
error: write /proc/30031/attr/current: invalid argument
that is a result of that information subcommand (check-aa-profile
) should not be written to output.The text was updated successfully, but these errors were encountered: