I believe there may be some miscommunication earlier. Sergio tried on a jammy vm. Here is what i tried, and i was unable to reproduce:
1. lxc launch ubuntu:jammy --vm --config limits.memory=4GiB cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.5 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.5 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; UBUNTU_CODENAME=jammy 2. apt update && apt full-upgrade 3. apt install clamav clamav-daemon 4. verified that everything is installed and running: 4a. aa-status:aa-status apparmor module is loaded. 41 profiles are loaded. 41 profiles are in enforce mode. <snip> /usr/sbin/clamd <snip> 2 processes have profiles defined. 2 processes are in enforce mode. /usr/bin/freshclam (379) /usr/sbin/clamd (399) 4b. sudo service clamav-daemon status ● clamav-daemon.service - Clam AntiVirus userspace daemon Loaded: loaded (/lib/systemd/system/clamav-daemon.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/clamav-daemon.service.d └─extend.conf Active: active (running) since Mon 2025-01-13 18:35:39 UTC; 14s ago 4c. ls /var/run/clamav/ clamd.ctl 5. rebooted vm 6. verification: 6a. aa-status apparmor module is loaded. 41 profiles are loaded. 41 profiles are in enforce mode. <snip> /usr/sbin/clamd <snip> 2 processes are in enforce mode. /usr/bin/freshclam (380) /usr/sbin/clamd (400) 6b. sudo service clamav-daemon status ● clamav-daemon.service - Clam AntiVirus userspace daemon Loaded: loaded (/lib/systemd/system/clamav-daemon.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/clamav-daemon.service.d └─extend.conf Active: active (running) since Mon 2025-01-13 18:38:54 UTC; 2min 29s ago 6c. ls /var/run/clamav/ clamd.ctl Could you provide the following information to help us see what may be different in your environment? * output from aa-status (this will help see if apparmor is doing something) * ls -alh /var/run/clamav (maybe an owernship issue somehow? maybe?) * service clamav-daemon status * any more logs or information? * if anything is changed in your system related to an install. you mentioned "my company", is it possible there's more restrictive configuration in a your corporate image than our free image (lxc uses images from cloud-images.ubuntu.com/releases/$SUITE/. by default LXC will use the latest serial. you can check that at /etc/cloud/build.info) sorry we haven't been able to reproduce so far -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076875 Title: creation of directory /var/run/clamav blocked by apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2076875/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
