KA systemd service is not detecting containers on reboot

[seswarrajan]

Bug Report

General Information

• Ubuntu VM

To Reproduce

1. Onboard a VM in systemd mode (This will install KubeArmor as well)
2. Now install 1 or 2 containers(like nginx/ubuntu/anything)
3. Now restart KubeArmor service.

Expected behavior

KA service should immediately identify the running containers.

Actual behavior

KA is not able to identify/recognise the containers which are running already and containers which are run after KA is getting recognised.

[rkcoder101]

Hi, I am planning to reproduce this issue locally and investigate it. I will update this thread with findings or questions.

[rksharma95]

@seswarrajan @rkcoder101 the issue is not reproducible.

Test result

PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian

$ uname -r
5.15.0-91-generic

vagrant@kubearmor-dev-next:~$ sudo systemctl status kubearmor                                                                                                                  [120/120]
● kubearmor.service - KubeArmor                                                                                                                                                         
     Loaded: loaded (/lib/systemd/system/kubearmor.service; disabled; vendor preset: enabled)                                                                                           
     Active: active (running) since Tue 2025-12-23 07:59:59 UTC; 2min 52s ago                                                                                                           
   Main PID: 2778 (kubearmor)                                                                                                                                                           
      Tasks: 17 (limit: 4558)                                                                                                                                                           
     Memory: 154.5M                                                                                                                                                                     
        CPU: 4.737s                                                                                                                                                                     
     CGroup: /system.slice/kubearmor.service                                                                                                                                            
             └─2778 /opt/kubearmor/kubearmor                                                                                                                                            
                                                                                                                                                                                        
Dec 23 08:00:02 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:02.124718        INFO        Verifying Docker API client version: 1.51                                             
Dec 23 08:00:02 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:02.130046        WARN        Docker client (1.51) and Docker server (1.52) API versions don't match                
Dec 23 08:00:02 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:02.137041        INFO        Initialized Docker Handler (version: 1.51)                                            
Dec 23 08:00:02 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:02.137741        INFO        Using unix:///var/run/docker.sock for monitoring containers                           
Dec 23 08:00:02 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:02.137779        INFO        Started to monitor Docker events                                                      
Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.137973        INFO        Started to monitor container security policies on gRPC                                
Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.138220        INFO        Started to monitor host security policies on gRPC                                     
Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.138598        INFO        Started to serve gRPC-based log feeds                                                 
vagrant@kubearmor-dev-next:~$ sudo journalctl -u kubearmor -f                                                                                                                           
Dec 23 08:00:02 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:02.124718        INFO        Verifying Docker API client version: 1.51                                             
Dec 23 08:00:02 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:02.130046        WARN        Docker client (1.51) and Docker server (1.52) API versions don't match                
Dec 23 08:00:02 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:02.137041        INFO        Initialized Docker Handler (version: 1.51)                                            
Dec 23 08:00:02 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:02.137741        INFO        Using unix:///var/run/docker.sock for monitoring containers                           
Dec 23 08:00:02 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:02.137779        INFO        Started to monitor Docker events                                                      
Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.137973        INFO        Started to monitor container security policies on gRPC                                
Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.138220        INFO        Started to monitor host security policies on gRPC                                     
Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.138598        INFO        Started to serve gRPC-based log feeds                                                 
Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.138642        INFO        Initialized KubeArmor                                                                 
Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.138817        WARN        Policies dir not found for restoration                                                
Dec 23 08:03:15 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:03:15.200759        INFO        Successfully added visibility map with key={PidNS:4026532312 MntNS:4026532259} to the 
kernel                                                                                                                                                                                  
Dec 23 08:03:15 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:03:15.200809        INFO        [ProtectProc] Registered container with id: 68fc0b4c6d6967f90790a3de1b12e20c78ce2562ba
3dcfa0e1dd270b680e5c0a                                                                                                                                                                  
Dec 23 08:03:15 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:03:15.200816        INFO        Detected a container (added/68fc0b4c6d69)                                             
^C                                                                                                                                                                                      
vagrant@kubearmor-dev-next:~$ sudo journalctl -u kubearmor -f                                                                                                                           
Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.138220        INFO        Started to monitor host security policies on gRPC                                     
Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.138598        INFO        Started to serve gRPC-based log feeds

Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.138642        INFO        Initialized KubeArmor                                                         [81/120]
Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.138817        WARN        Policies dir not found for restoration                                                
Dec 23 08:03:15 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:03:15.200759        INFO        Successfully added visibility map with key={PidNS:4026532312 MntNS:4026532259} to the 
kernel                                                                                                                                                                                  
Dec 23 08:03:15 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:03:15.200809        INFO        [ProtectProc] Registered container with id: 68fc0b4c6d6967f90790a3de1b12e20c78ce2562ba
3dcfa0e1dd270b680e5c0a                                                                                                                                                                  
Dec 23 08:03:15 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:03:15.200816        INFO        Detected a container (added/68fc0b4c6d69)                                             
Dec 23 08:03:50 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:03:50.684699        INFO        Successfully added visibility map with key={PidNS:4026532526 MntNS:4026532523} to the 
kernel                                                                                                                                                                                  
Dec 23 08:03:50 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:03:50.684758        INFO        [ProtectProc] Registered container with id: 868a22392b93b9ef7a07ba018967baf0dd14f7e550
acb8875bb01cee8fc5bd09                                                                                                                                                                  
Dec 23 08:03:50 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:03:50.684772        INFO        Detected a container (added/868a22392b93)                                             
^C                                                                                                                                                                                      
vagrant@kubearmor-dev-next:~$ sudo journalctl -u kubearmor -f                                                                                                                           
Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.138220        INFO        Started to monitor host security policies on gRPC
Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.138598        INFO        Started to serve gRPC-based log feeds
Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.138642        INFO        Initialized KubeArmor
Dec 23 08:00:03 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:00:03.138817        WARN        Policies dir not found for restoration
Dec 23 08:03:15 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:03:15.200759        INFO        Successfully added visibility map with key={PidNS:4026532312 MntNS:4026532259} to the 
kernel
Dec 23 08:03:15 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:03:15.200809        INFO        [ProtectProc] Registered container with id: 68fc0b4c6d6967f90790a3de1b12e20c78ce2562ba
3dcfa0e1dd270b680e5c0a
Dec 23 08:03:15 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:03:15.200816        INFO        Detected a container (added/68fc0b4c6d69)
Dec 23 08:03:50 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:03:50.684699        INFO        Successfully added visibility map with key={PidNS:4026532526 MntNS:4026532523} to the 
kernel
Dec 23 08:03:50 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:03:50.684758        INFO        [ProtectProc] Registered container with id: 868a22392b93b9ef7a07ba018967baf0dd14f7e550
acb8875bb01cee8fc5bd09
Dec 23 08:03:50 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:03:50.684772        INFO        Detected a container (added/868a22392b93)
Dec 23 08:04:32 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:04:32.093033        INFO        Got a signal to terminate KubeArmor
Dec 23 08:04:32 kubearmor-dev-next systemd[1]: Stopping KubeArmor...
Dec 23 08:04:32 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:04:32.445818        WARN        Ring Buffer closed, exiting TraceEvents epoll wait: file already closed
Dec 23 08:04:32 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:04:32.448294        INFO        Destroyed BPF-LSM Enforcer
Dec 23 08:04:32 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:04:32.448368        INFO        Stopped KubeArmor Enforcer
Dec 23 08:04:32 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:04:32.448574        WARN        Perf Buffer closed, exiting TraceSyscall epoll wait: file already closed
Dec 23 08:04:34 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:04:34.548712        INFO        Stopped KubeArmor Monitor
Dec 23 08:04:34 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:04:34.548759        INFO        Terminated KubeArmor
Dec 23 08:04:36 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:04:36.552416        INFO        Terminated the gRPC service
Dec 23 08:04:36 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:04:36.552459        INFO        Stopped KubeArmor Logger
Dec 23 08:04:36 kubearmor-dev-next kubearmor[2778]: 2025-12-23 08:04:36.552489        INFO        Waiting for routine terminations

Dec 23 08:04:36 kubearmor-dev-next systemd[1]: kubearmor.service: Deactivated successfully.
Dec 23 08:04:36 kubearmor-dev-next systemd[1]: Stopped KubeArmor.
Dec 23 08:04:36 kubearmor-dev-next systemd[1]: kubearmor.service: Consumed 11.223s CPU time. 
Dec 23 08:04:36 kubearmor-dev-next systemd[1]: Started KubeArmor.
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.726732        WARN        Error creating kubernetes config, invalid configuration: no configuration has been pro
vided, try setting KUBERNETES_MASTER environment variable
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.726875        INFO        Arguments [alertThrottling:true annotateResources:false bpfFsPath:/sys/fs/bpf cluster:
default coverageTest:false criSocket: debug:false defaultCapabilitiesPosture:audit defaultFilePosture:audit defaultNetworkPosture:audit defaultPostureLogs:true enableIMA:false enableKu
beArmorHostPolicy:false enableKubeArmorPolicy:true enableKubeArmorStateAgent:false enableKubeArmorVm:false enableNRI:false enableUSBDeviceHandler:false enforcerAlerts:true gRPC:32767 h
ost:kubearmor-dev-next hostDefaultCapabilitiesPosture:audit hostDefaultDevicePosture:audit hostDefaultFilePosture:audit hostDefaultNetworkPosture:audit hostVisibility:default initTimeo
ut:60s k8s:true kubeconfig: logPath:none lsm:bpf,apparmor,selinux machineIDPath:/etc/machine-id maxAlertPerSec:10 nriIndex:99 nriSocket: procfsMount:/proc seLinuxProfileDir:/tmp/kubear
mor.selinux throttleSec:30 tlsCertPath:/var/lib/kubearmor/tls tlsCertProvider:self tlsEnabled:false untrackedNs:kube-system,kubearmor useOCIHooks:false visibility:process,file,network,
capabilities]
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.726907        INFO        setting config from file [kubearmor.yaml]
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.726996        INFO        Configuration [{Cluster: Host: GRPC: TLSEnabled:false TLSCertPath: TLSCertProvider: Lo
gPath: SELinuxProfileDir: CRISocket: NRISocket: NRIIndex: NRIEnabled:false Visibility: HostVisibility: EnableIMA:false Policy:false HostPolicy:false KVMAgent:false K8sEnv:false Debug:f
alse DefaultFilePosture: DefaultNetworkPosture: DefaultCapabilitiesPosture: HostDefaultFilePosture: HostDefaultNetworkPosture: HostDefaultCapabilitiesPosture: HostDefaultDevicePosture:
 CoverageTest:false ConfigUntrackedNs:[] LsmOrder:[] BPFFsPath: EnforcerAlerts:false DefaultPostureLogs:false InitTimeout: StateAgent:false UseOCIHooks:false AlertThrottling:false MaxA
lertPerSec:0 ThrottleSec:0 AnnotateResources:false ProcFsMount: MachineIDPath: USBDeviceHandler:false}]
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.727027        INFO        Final Configuration [{Cluster:default Host:kubearmor-dev-next GRPC:32767 TLSEnabled:fa
lse TLSCertPath:/var/lib/kubearmor/tls TLSCertProvider:self LogPath:none SELinuxProfileDir: CRISocket: NRISocket: NRIIndex:99 NRIEnabled:false Visibility:process,file,network,capabilit
ies HostVisibility:process,file,network,capabilities EnableIMA:false Policy:true HostPolicy:true KVMAgent:false K8sEnv:false Debug:false DefaultFilePosture:audit DefaultNetworkPosture:
audit DefaultCapabilitiesPosture:audit HostDefaultFilePosture:audit HostDefaultNetworkPosture:audit HostDefaultCapabilitiesPosture:audit HostDefaultDevicePosture:audit CoverageTest:fal
se ConfigUntrackedNs:[kube-system kubearmor] LsmOrder:[bpf apparmor selinux] BPFFsPath:/sys/fs/bpf EnforcerAlerts:true DefaultPostureLogs:true InitTimeout:60s StateAgent:false UseOCIHo
oks:false AlertThrottling:true MaxAlertPerSec:10 ThrottleSec:30 AnnotateResources:false ProcFsMount:/proc MachineIDPath:/etc/machine-id USBDeviceHandler:false}]
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.727041        INFO        Final Configuration [{Cluster:default Host:kubearmor-dev-next GRPC:32767 TLSEnabled:fa
lse TLSCertPath:/var/lib/kubearmor/tls TLSCertProvider:self LogPath:none SELinuxProfileDir: CRISocket: NRISocket: NRIIndex:99 NRIEnabled:false Visibility:process,file,network,capabilit
ies HostVisibility:process,file,network,capabilities EnableIMA:false Policy:true HostPolicy:true KVMAgent:false K8sEnv:false Debug:false DefaultFilePosture:audit DefaultNetworkPosture:
audit DefaultCapabilitiesPosture:audit HostDefaultFilePosture:audit HostDefaultNetworkPosture:audit HostDefaultCapabilitiesPosture:audit HostDefaultDevicePosture:audit CoverageTest:fal
se ConfigUntrackedNs:[kube-system kubearmor] LsmOrder:[bpf apparmor selinux] BPFFsPath:/sys/fs/bpf EnforcerAlerts:true DefaultPostureLogs:true InitTimeout:60s StateAgent:false UseOCIHo
oks:false AlertThrottling:true MaxAlertPerSec:10 ThrottleSec:30 AnnotateResources:false ProcFsMount:/proc MachineIDPath:/etc/machine-id USBDeviceHandler:false}]
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.808275        INFO        Node Name: kubearmor-dev-next
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.808490        INFO        Node IP: 10.0.2.15
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.808507        INFO        Node ID: 9be64e0455a46bfca6526810f9120d2c5d015f0e8713ab10207e37521cacfc6d
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.808521        INFO        OS Image: Ubuntu 22.04.3 LTS
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.808534        INFO        Kernel Version: 5.15.0-91-generic
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.808913        INFO        Initialized KubeArmor Logger
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.810603        INFO        Detected mounted BPF filesystem at /sys/fs/bpf

Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.810985        INFO        Initializing eBPF system monitor
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.832897        INFO        Successfully added visibility map with key={PidNS:0 MntNS:0} to the kernel
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.854558        INFO        Successfully added visibility map with key={PidNS:12648430 MntNS:12648430} to the kern
el
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.855112        INFO        Alert Throttling configured {alertThrottling:true, maxAlertPerSec:10, throttleSec:30}
Dec 23 08:04:36 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:36.855319        INFO        eBPF system monitor object file path: /opt/kubearmor/BPF/system_monitor.bpf.o
Dec 23 08:04:37 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:37.290838        INFO        Initialized the eBPF system monitor
Dec 23 08:04:38 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:38.320399        INFO        Initialized KubeArmor Monitor
Dec 23 08:04:38 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:38.320449        INFO        Started to monitor system events
Dec 23 08:04:38 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:38.323190        INFO        Supported LSMs: lockdown,capability,apparmor,bpf
Dec 23 08:04:38 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:38.897682        INFO        Starting TraceEvents from BPF LSM Enforcer
Dec 23 08:04:38 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:38.920811        INFO        Initialized BPF-LSM Enforcer
Dec 23 08:04:38 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:38.920871        INFO        Initialized KubeArmor Enforcer
Dec 23 08:04:38 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:38.920884        INFO        Started to protect a host and containers
Dec 23 08:04:38 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:38.967535        INFO        Starting TraceEvents from Exec Presets
Dec 23 08:04:38 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:38.980948        INFO        Starting TraceEvents from ProtectProc Presets
Dec 23 08:04:38 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:38.989471        INFO        Starting TraceEvents from AnonMapExec Presets
Dec 23 08:04:39 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:39.003068        INFO        Starting TraceEvents from FilelessExec Presets
Dec 23 08:04:39 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:39.016692        INFO        Initialized Presets
Dec 23 08:04:39 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:39.016767        INFO        Namespace container_namespace visibiliy configured {File:true Process:true Network:tru
e Capabilities:true DNS:false IMA:false}
Dec 23 08:04:39 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:39.016849        INFO        Starting TraceEvents from ProtectEnv Presets
Dec 23 08:04:39 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:39.017347        INFO        Verifying Docker API client version: 1.51
Dec 23 08:04:39 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:39.023981        WARN        Docker client (1.51) and Docker server (1.52) API versions don't match
Dec 23 08:04:39 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:39.025646        INFO        Initialized Docker Handler (version: 1.51)
Dec 23 08:04:39 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:39.040834        INFO        Successfully added visibility map with key={PidNS:4026532526 MntNS:4026532523} to the 
kernel
Dec 23 08:04:39 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:39.040864        INFO        [ProtectProc] Registered container with id: 868a22392b93b9ef7a07ba018967baf0dd14f7e550
acb8875bb01cee8fc5bd09
Dec 23 08:04:39 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:39.040873        INFO        Detected a container (added/868a22392b93)
Dec 23 08:04:39 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:39.068958        INFO        Successfully added visibility map with key={PidNS:4026532312 MntNS:4026532259} to the 
kernel
Dec 23 08:04:39 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:39.069068        INFO        [ProtectProc] Registered container with id: 68fc0b4c6d6967f90790a3de1b12e20c78ce2562ba
3dcfa0e1dd270b680e5c0a
Dec 23 08:04:39 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:39.069169        INFO        Detected a container (added/68fc0b4c6d69)
Dec 23 08:04:39 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:39.069210        INFO        Using unix:///var/run/docker.sock for monitoring containers
Dec 23 08:04:39 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:39.069262        INFO        Started to monitor Docker events
Dec 23 08:04:40 kubearmor-dev-next kubearmor[3332]: 2025-12-23 08:04:40.069771        INFO        Started to monitor container security policies on gRPC