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
Describe the bug
We can access the store 9p mount just fine from the host, however, the systemd services cannot access it.
When the service tries to access the mount, this error message pops out in the journal:
9pnet_virtio: no channels available for device nix-store
I tried these recommandations https://superuser.com/questions/1317119/qemu-share-folder-9pnet-virtio-no-channels-available-for-device . No luck.
I tried:
ProtectSystem
It feels like a weird systemd/9p interaction to me. I searched the systemd bug tracker, there's no related issue, opened or close.
This issue does not manifest in Ubuntu or Debian. They're using older systemd versions.
We probably should try to find a minimal reproducer and poke upstream with that.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
We can access the store 9p mount just fine from the host, however, the systemd services cannot access it.
When the service tries to access the mount, this error message pops out in the journal:
I tried these recommandations https://superuser.com/questions/1317119/qemu-share-folder-9pnet-virtio-no-channels-available-for-device . No luck.
I tried:
ProtectSystem
to falseIt feels like a weird systemd/9p interaction to me. I searched the systemd bug tracker, there's no related issue, opened or close.
This issue does not manifest in Ubuntu or Debian. They're using older systemd versions.
We probably should try to find a minimal reproducer and poke upstream with that.
The text was updated successfully, but these errors were encountered: