mirror of
https://github.com/containers/youki
synced 2024-05-22 23:46:08 +02:00
601df9ecd3
* Set cgroups path for tenant containers from main container Signed-off-by: Yashodhan Joshi <yjdoc2@gmail.com> * Ignore new_user_ns for creating cgroups path Signed-off-by: Yashodhan Joshi <yjdoc2@gmail.com> * Remove user_ns param completely Signed-off-by: Yashodhan Joshi <yjdoc2@gmail.com> * Add tests in podman rootless for exec Signed-off-by: Yashodhan Joshi <yjdoc2@gmail.com> * Fix add_task implementation for cgroups v2 and systemd Signed-off-by: Yashodhan Joshi <yjdoc2@gmail.com> * minor refactor in tenant builder Signed-off-by: Yashodhan Joshi <yjdoc2@gmail.com> * Add unit test for systemd add_task function Signed-off-by: Yashodhan Joshi <yjdoc2@gmail.com> * Fix task addition to properly add tasks via dbus api Signed-off-by: Yashodhan Joshi <yjdoc2@gmail.com> * Fix cross cotainers for tests running Signed-off-by: Yashodhan Joshi <yjdoc2@gmail.com> --------- Signed-off-by: Yashodhan Joshi <yjdoc2@gmail.com>
15 lines
838 B
Bash
15 lines
838 B
Bash
#!/bin/sh
|
|
|
|
# This hack script is the dummy busctl command used when running tests with cross containers.
|
|
|
|
# The issue is that we cannot run systemd or dbus inside the test container without a lot
|
|
# of hacks. For one specific test - test_task_addition, we need to check that the task
|
|
# addition via systemd manager works. We mount the host dbus socket in the test container, so
|
|
# dbus calls work, but for the initial authentication, we use busctl which needs dbus and systemd
|
|
# to be present and running. So instead of doing all that, we simply run the container with the
|
|
# actual test running user's uid/gid and here we echo the only relevant line from busctl's
|
|
# output, using id to get the uid. This is a hack, but less complex than actually setting up
|
|
# and running the systemd+dbus inside the container.
|
|
|
|
echo "OwnerUID=$(id -u)"
|