From samuel.mercier@mongodb.com 

i did run into one rough edge. i have to port-forward in order expose port 22 for ssh to connect via tramp (emacs' version of remote editing). confusingly even though i'm able to run the docker container via the docker CLI after it was created by vscode. vscode seems to be doing some witchcraft in order to enable the port-forwarding of the ssh port but that witchcraft stops whenever i quit vscode.i have a few reasons to think vscode is doing something strange here: *  the container is still reported as running by docker after i quit vscode (including long after indicating it's not just ramping down) 

• ssh connections disconnect instantly
• the terminal for the container within the docker desktop application remains open and live (which doesn't use ssh)

all of which indicates that it is vscode that providing the port forwarding behavior. i would prefer not to be running vscode.is there a way to provide port forwarding functionality without vscode? a cursory google search said that this could only be done within the container definition not after the containers been defined, and docker run similarly doesn't seem to report a way to port forward.