[ https://ovirt-jira.atlassian.net/browse/OVIRT-2917?page=com.atlassian.jir... ] Ales Musil commented on OVIRT-2917: ----------------------------------- No, vagrant is not going to be used. The original question was if we can use CI container that runs vagrant VM. Because this option is not good idea as we were told, we would like to have privileged container running directly on CI. As requested here is list of services that we run in container: UNIT LOAD ACTIVE SUB DESCRIPTION dbus.service loaded active running D-Bus System Message Bus NetworkManager.service loaded active running Network Manager selinux-autorelabel-mark.service loaded active exited Mark the need to relabel after reboot systemd-journald.service loaded active running Journal Service systemd-resolved.service loaded active running Network Name Resolution systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories systemd-udevd.service loaded active running udev Kernel Device Manager LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 7 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125)