Here’s a specific example I just ran into…
I used your instructions with the torizon/debian:2-bullseye container to get the SSH capability setup. I installed a bunch of stuff needed to support my development. Here is the Dockerfile and I tagged it base-model17xx-dev:
FROM --platform=linux/arm torizon/debian:2-bullseye
RUN apt-get update && apt-get install apt-utils
RUN apt-get install -y openssh-server
RUN mkdir /var/run/sshd
RUN echo 'root:root' | chpasswd
RUN sed -i 's/#PermitRootLogin prohibit-password/PermitRootLogin yes/' /etc/ssh/sshd_config
ENV NOTVISIBLE "in users profile"
RUN echo "export VISIBLE=now" >> /etc/profile
RUN apt-get install -y libc6 libstdc++6 python2-minimal ca-certificates tar
RUN apt-get install curl wget
RUN apt-get install bc bison build-essential flex git
RUN apt-get install libcairo2-dev libfl-dev libfreetype-dev libjansson-dev libts-dev
RUN apt-get install nano neofetch netbase sudo
RUN apt-get install lighttpd
RUN apt-get install python net-tools
EXPOSE 22
EXPOSE 80
CMD ["/usr/sbin/sshd", "-D"]
Then I ran this container using:
docker run -d -p 2222:22/tcp -p 8080:80/tcp --name model17xx-dev-2 base-model17xx-dev
That works fine. I cloned my codebase and got VS Code remote running. Now I find out that none of the hardware devices I need are mapped to the container. Ugh. Apparently I needed to run the container with:
docker run -d -p 2222:22/tcp -p 8080:80/tcp --privileged -v /dev:/dev --name model17xx-dev-2 base-model17xx-dev
There is no way once a container has been run to “restart” it with a different parameter? So all my edits in the first container are now a dead end?
Am I missing something? This workflow seems ridiculous… I have to know every detail about what my container needs before I do any work within it or I risk having to go back and recreate it all again.
EDIT: I found this hack. 
[tried it and it doesn’t seem to work for the /dev mount anyway]