Hello.
Is it possible to configure exclusive single-user access to containers?
Suppose I'd like to invite users to work in their personal containers. Just to avoid possible confusion, let's call such users 'guests'.
- A guest shouldn't be able to ssh to the host, they should be able to ssh only into the container.
- I'd like each container have an owner and let them and only them be able to auth into the container. So each container is owned by only 1 guest (but a guest may own multiple containers).
- Each container's image is identical, they have some built-in generic user, whose name is the same in each container. Guests log-in as that user.
- Each guest has their own ssh key.
So, basically, I need a mapping of ssh-keys. which should be tied to specific containers.
It is acceptable to make guests remember which port to connect to in order to get into specific container, but I'd rather let them rely on your system where a guest can specify instance-name right in the ssh connection string.
Does ssh2incus allow such a scenario of use?
Hello.
Is it possible to configure exclusive single-user access to containers?
Suppose I'd like to invite users to work in their personal containers. Just to avoid possible confusion, let's call such users 'guests'.
So, basically, I need a mapping of ssh-keys. which should be tied to specific containers.
It is acceptable to make guests remember which port to connect to in order to get into specific container, but I'd rather let them rely on your system where a guest can specify
instance-nameright in the ssh connection string.Does ssh2incus allow such a scenario of use?