You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @QuaxEros, I am creating this issue to address the errors you reported in #29. That issue also has some additional context for what's causing the errors and what functionality is affected.
After a bit of research, I think I found a way to properly get rid of this error without making the container privileged (which would impact its security). See:
To my understanding, you would want to set security.syscalls.intercept.mknod to true.
I didn't manage to figure out whether this will work with current kernels (6.x). So I guess you will just have to try and see.
If you find the time to test this solution then great. If not - not a big deal. I just wanted to have this issue open so other people using LXC containers would be able to find it and perhaps elaborate on whether the solution works or not, or propose alternative ways to deal with ithe issue.
Generally this error is insignificant and won't prevent geoip-shell from functioning correctly, however it may be nicer to avoid having it printed.
The text was updated successfully, but these errors were encountered:
I can clone my LXC containers from backup onto homelab which runs same Proxmox version so same kernel and test. Probably tomorrow, if not the day after.. I could do more testing as soon as i have that setup.
Hi @QuaxEros, I am creating this issue to address the errors you reported in #29. That issue also has some additional context for what's causing the errors and what functionality is affected.
After a bit of research, I think I found a way to properly get rid of this error without making the container privileged (which would impact its security). See:
https://documentation.ubuntu.com/lxd/en/stable-5.0/syscall-interception/
To my understanding, you would want to set
security.syscalls.intercept.mknod
totrue
.I didn't manage to figure out whether this will work with current kernels (6.x). So I guess you will just have to try and see.
If you find the time to test this solution then great. If not - not a big deal. I just wanted to have this issue open so other people using LXC containers would be able to find it and perhaps elaborate on whether the solution works or not, or propose alternative ways to deal with ithe issue.
Generally this error is insignificant and won't prevent geoip-shell from functioning correctly, however it may be nicer to avoid having it printed.
The text was updated successfully, but these errors were encountered: