Skip to content

Conversation

@traylenator
Copy link
Contributor

Even a --privileged rootless podman container is unable to do some operations.

If podman_rootful is set true (default false) then /run/podman/podman.socket

What cannot be done in a privileged rootless container ? Obvious one is interact with kernel modules for instance.

The vast majority of modules will be fine with rootless containers and its much closer to what folk typically run on the their laptops so the current behaviour makes a sensible default.

Even a `--privileged` rootless podman container is unable to do some
operations.

If `podman_rootful` is set `true` (default false) then
`/run/podman/podman.socket`

What cannot be done in a privileged rootless container ? Obvious one is
install kernel modules for instance.

The vast majority of modules will be fine with rootless containers and
its much closer to what folk typically run on the their laptops so the
current default makes a sensible default.
run: |
systemctl start --user podman.socket
echo "DOCKER_HOST=unix:///run/user/$(id -u)/podman/podman.sock" >> "$GITHUB_ENV"
- if: ${{ inputs.podman_rootful }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we skip the action above if rootful is true? We don't need a system- and a user- service

@traylenator
Copy link
Contributor Author

While this works on my laptap if I set up the podman socket this way it unfortunately hangs when trying the SSH into the container in CI. voxpupuli/puppet-cvmfs#230
Maybe I should just switch to vagrant

@traylenator
Copy link
Contributor Author

Another alternative, run sudo podman. May as well in reality if attempting to use the root owned socket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants