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
They started right after the apt install, I did not configure any NFS share yet.
I tried to removed all the stacks running on that server, except the Periphery agent, but traces are still reported in the shell.
Only ways to stop those traces is to either disable the Periphery agent or remove the nfs-kernel-server package.
From Komodo UI, looks like everything is working as expected with proper stats being reported by the server.
My setup is a Debian 12 VM running in a Proxmox 8 setup.
Is there something I can do to help investigate that issue?
Sorry if this issue is lacking debugging on my side, I am pretty new to Komodo and running containers on Linux (I have been using Windows or WSL2 up until recently).
The text was updated successfully, but these errors were encountered:
My secondary Debian server is running multiple stacks fine but since adding
nfs-kernel-server
my shell gets spammed with AppArmor audit traces likeThe mentioned PID matches the Periphery container on that secondary server.
They started right after the apt install, I did not configure any NFS share yet.
I tried to removed all the stacks running on that server, except the Periphery agent, but traces are still reported in the shell.
Only ways to stop those traces is to either disable the Periphery agent or remove the
nfs-kernel-server
package.From Komodo UI, looks like everything is working as expected with proper stats being reported by the server.
My setup is a Debian 12 VM running in a Proxmox 8 setup.
Is there something I can do to help investigate that issue?
Sorry if this issue is lacking debugging on my side, I am pretty new to Komodo and running containers on Linux (I have been using Windows or WSL2 up until recently).
The text was updated successfully, but these errors were encountered: