Feature or enhancement request details
At present, when a user runs a container with --ssh, container-runtime-linux reads the permission bits on the host SSH_AUTH_SOCK and establishes the same permissions on the container end of the socket relay.
We should do this for all host-to-container socket mounts; otherwise, the sockets are unusable by non-root workloads.
Code of Conduct
Feature or enhancement request details
At present, when a user runs a container with
--ssh, container-runtime-linux reads the permission bits on the host SSH_AUTH_SOCK and establishes the same permissions on the container end of the socket relay.We should do this for all host-to-container socket mounts; otherwise, the sockets are unusable by non-root workloads.
Code of Conduct