When connected via ssh, "pip" (and other tools) should be available, just like they are in a "normal" terminal.
Also all the environment variables that are present in normal terminal sessions should be available in a ssh session (or in a shell opened via ssh).
Trying to execute "pip" gives a "command not found" error when connected through ssh, but the command works properly when executed in a normal terminal.
The ssh daemon is running in a docker container based on the image
It is exposed as port 30022.
/bin/bash as an interactive terminal into the container works as expected with all the tools available and environment variables set. The user inside the container is the default (root) user - same when connecting through ssh.
The ssh connection is done using a rsa keypair with the pubkey added in the container's
ssh -p 30022 root@localhost, or
ssh -p 30022 root@localhost -t "bash -l" didn't give a shell with the desired behavior.
su - in a ssh session didn't help.
source /root/.bashrc in a ssh session didn't help either.