-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[macOS] Error: for attach: setxattr #13631
Comments
Does it work when you remove the |
Yes it does. What is this z ? |
z stand for selinux relabeling which requires extended attributes. I am not sure if virtiofs support this. If it works without out it you do not need it. |
Mac file systems based on Plan 9 does not support SELinux labeling Currently the volumes mounted into the VM are labeled as nfs_t, and all containers are allowed to read/write the content. |
Hey I am currently trying to support macOS and linux (fedora) machines using the same |
Please open a new issue. Do not add to a closed issue. Podman play kube should work on a MacOS |
Currently, podman does not support SELinux labels due to how they mount volumes. This causes the build to fail, with `lsetxattr` being unsupported. The relevant podman issue is [here](containers/podman#13631), and the description of the issue and volume mounts is [here](containers/podman#13631 (comment)).
Currently, podman does not support SELinux labels due to how they mount volumes. This causes the build to fail, with `lsetxattr` being unsupported. The relevant podman issue is [here](containers/podman#13631), and the description of the issue and volume mounts is [here](containers/podman#13631 (comment)). Closes cross-rs#756.
Currently, podman does not support SELinux labels due to how they mount volumes. This causes the build to fail, with `lsetxattr` being unsupported. The relevant podman issue is [here](containers/podman#13631), and the description of the issue and volume mounts is [here](containers/podman#13631 (comment)). Closes cross-rs#756.
Depending on how docker is installed and configured but also the hardening applied to the workstation, docker might not be able to mount the code base properly in the container. As such, the user could end up with a error similar to the following: ``` ❯ make lint --8<-- >>>> Entering build container: lint-packaging-scripts time docker run --rm --tty -i -v ~/.ssh/:/root/.ssh:delegated,z -v /workspace/github.com/grafana/mimir/.cache:/go/cache:delegated,z -v /workspace/github.com/grafana/mimir/.pkg:/go/pkg:delegated,z -v /workspace/github.com/grafana/mimir:/go/src/github.com/grafana/mimir:delegated,z grafana/mimir-build-image GOOS=darwin GOARCH=amd64 BINARY_SUFFIX="" lint-packaging-scripts; Error: error preparing container 9c7c78b35ac936b65510dec180a81f6f38ea98e027d7049012f73f7ac31f885d for attach: lsetxattr /workspace/github.com/grafana/mimir/.cache: operation not supported real 0m0,719s user 0m0,046s sys 0m0,021s ``` This error could also be trigger when using podman as an alternative for docker. See: containers/podman#13631 Signed-off-by: Wilfried Roset <wilfriedroset@users.noreply.github.com>
Depending on how docker is installed and configured but also the hardening applied to the workstation, docker might not be able to mount the code base properly in the container. As such, the user could end up with a error similar to the following: ``` ❯ make lint --8<-- >>>> Entering build container: lint-packaging-scripts time docker run --rm --tty -i -v ~/.ssh/:/root/.ssh:delegated,z -v /workspace/github.com/grafana/mimir/.cache:/go/cache:delegated,z -v /workspace/github.com/grafana/mimir/.pkg:/go/pkg:delegated,z -v /workspace/github.com/grafana/mimir:/go/src/github.com/grafana/mimir:delegated,z grafana/mimir-build-image GOOS=darwin GOARCH=amd64 BINARY_SUFFIX="" lint-packaging-scripts; Error: error preparing container 9c7c78b35ac936b65510dec180a81f6f38ea98e027d7049012f73f7ac31f885d for attach: lsetxattr /workspace/github.com/grafana/mimir/.cache: operation not supported real 0m0,719s user 0m0,046s sys 0m0,021s ``` This error could also be trigger when using podman as an alternative for docker. See: containers/podman#13631 Signed-off-by: Wilfried Roset <wilfriedroset@users.noreply.github.com> Signed-off-by: Wilfried Roset <wilfriedroset@users.noreply.github.com>
To save people from struggling, |
Hopefully, this is only a temporary solution as noted by podman upstream in containers/podman#13631 (comment).
Hopefully, this is only a temporary solution as noted by podman upstream in containers/podman#13631 (comment).
Hopefully, this is only a temporary solution as noted by podman upstream in containers/podman#13631 (comment).
Hopefully, this is only a temporary solution as noted by podman upstream in containers/podman#13631 (comment).
Hopefully, this is only a temporary solution as noted by podman upstream in containers/podman#13631 (comment).
Hopefully, this is only a temporary solution as noted by podman upstream in containers/podman#13631 (comment).
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
I tried to attach a folder for busybox ls (sanity check) in my MacOS laptop through podman
Steps to reproduce the issue:
2.podman run -it --volume /mnt/Users/vassilisanagnostopoulos/work:/share:z busybox ls
Describe the results you received:
Error: error preparing container cf050ad434f57d762d589b0bee8e4aee68682d7676f7ceaeb7b16ab8970b7d30 for attach: setxattr /mnt/Users/vassilisanagnostopoulos/work: operation not supported
Describe the results you expected:
To be an empty list, afterall work is empty
Additional information you deem important (e.g. issue happens only occasionally):
Podman installed through brew and updated everything through
brew update && brew upgrade
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (/~https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Darwin C02CH2W2MD6R.local 20.6.0 Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:31 PDT 2021; root:xnu-7195.141.2~5/RELEASE_X86_64 x86_64
The text was updated successfully, but these errors were encountered: