-
Notifications
You must be signed in to change notification settings - Fork 2
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
Permission denied issue #25
Comments
Can you try the latest lxcfs from the ganto/lxc4 COPR. As I said before, I assumed this to be an issue with lxcfs that seems to be fixed now. I cannot reproduce the error:
If this still happens for you please provide an exact step by step guide how to reproduce your error. |
Sorry for the long delay. Unfortunately, I can't confirm that lxd works in Fedora 31. Test machine 01
Test machine 02
After update to Fedora 31 (using dnf)
After waiting some time:
I'm at my wits' end. I can grant you access to both machines if it helps. And I can run all kind of test you suggest. I have similiar issues with various CentOS 8 machines and LXD.
|
Can you please check the output of |
Test machine 01 In /var/log/lxd/lxd.log I found:
And in /var/log/lxc/test01/console.log
Looks not good. Test machine 02 I found as well:
And in /var/log/lxd/test01/console.log
|
Ok, I thought so. See #21 for a "solution" aka work-around for this. You might want to ask upstream if this behavior is expected or if this is a bug. It's definitely not something that I can fix in the RPM packaging ;-) |
Ok, I used And I could start postfix just fine with lxcfs 4.0.4-0.2.fc31. Thanks for that work and information! But immediately I have another question: can you provide lxcfs 4.0.4 also for CentOS 8 and lxd 3.22 and 3.21? |
I just checked again and there is still a permission denied issue when you try to start a postfix process in lxd 3.22 hosted by CentOS 8 (8.2.2009) and Fedora 31. So you can't use postfix in a container at all.
The error message is:
/usr/libexec/postfix/postfix-script: line 127: /dev/null: Permission denied
We first discussed the issue an Apr. 6. Is there even a chance to fix the issue or is it just too big and unmanageable?
The text was updated successfully, but these errors were encountered: