Add better error reporting for common cases #59
Comments
mvo5
added a commit
to mvo5/containers-image-proxy-rs
that referenced
this issue
Jan 17, 2025
This commit adds a new SkopeoSpawnError that helps with tweaking the user-experience when e.g. skopeo is not installed. Partially closes: containers/composefs-rs#59 Signed-off-by: Michael Vogt <[email protected]>
mvo5
added a commit
to mvo5/containers-image-proxy-rs
that referenced
this issue
Jan 17, 2025
This commit adds a new SkopeoSpawnError that helps with tweaking the user-experience when e.g. skopeo is not installed. Partially closes: containers/composefs-rs#59 Signed-off-by: Michael Vogt <[email protected]>
allisonkarlitskaya
closed this as completed
in
containers/containers-image-proxy-rs@8f992d3
|
Silly github closed this automatically... |
mvo5
added a commit
to mvo5/composefs-rs
that referenced
this issue
Feb 14, 2025
This commit improves the UX of the error reporting when enabling fs-verity fails because the underlying filesystem does not support this. Here we currently just error with: ``` Inappropriate ioctl for device" ``` with the new code we error with: ``` Filesystem not supported by fs-verity ``` Note that the test relies on the fact that /dev/shm is not supported by fs-verity. Closes: containers#59
mvo5
added a commit
to mvo5/composefs-rs
that referenced
this issue
Feb 14, 2025
This commit improves the UX of the error reporting when enabling fs-verity fails because the underlying filesystem does not support this. Here we currently just error with: ``` Inappropriate ioctl for device" ``` with the new code we error with: ``` Filesystem not supported by fs-verity ``` Note that the test relies on the fact that /dev/shm is not supported by fs-verity. Closes: containers#59
mvo5
added a commit
to mvo5/composefs-rs
that referenced
this issue
Feb 17, 2025
This commit improves the UX of the error reporting when enabling fs-verity fails because the underlying filesystem does not support this. Here we currently just error with: ``` Inappropriate ioctl for device" ``` with the new code we error with: ``` Filesystem not supported by fs-verity ``` Note that the test relies on the fact that /dev/shm is not supported by fs-verity. Closes: containers#59 Signed-off-by: Michael Vogt <[email protected]>
mvo5
added a commit
to mvo5/composefs-rs
that referenced
this issue
Feb 19, 2025
This commit improves the UX of the error reporting when enabling fs-verity fails because the underlying filesystem does not support this. Here we currently just error with: ``` Inappropriate ioctl for device" ``` with the new code we error with: ``` Filesystem not supported by fs-verity ``` Note that the test relies on the fact that /dev/shm is not supported by fs-verity. Closes: containers#59 Signed-off-by: Michael Vogt <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have a few people trying out the examples lately and they tend to run into a couple of common issues for which we have terrible error messages:
The first one is 100% on us: we need a better error for that. The second one is arguably something to be fixed in containers-image-proxy-rs.
See also #25
The text was updated successfully, but these errors were encountered: