

The second easiest is Crouton which requires Developer mode, but can still maintain a lot of the system security features. The easiest is to enable SSH in Crostini and set up a port forward using the new options in the latest ChromeOS releases. You can use this if the Terminal no longer starts the container and you want to get onto it.)Īs you mentioned there are several options for accessing ChromeOS devices depending on what your goal is. (There is a way to manually start a container with CROSH and then use termina and then lxc. If the container is not started from the Terminal application, it is not possible to start port-forwarding. The Linux containers can break and not startup from the Terminal application. If you do get it working, remember to backup your Linux container. You have to manually start forwarding in the Linux settings tab after you have stopped the container. It is an inconvenience but the port-forwarding is not restored when you stop and then start the container. What you can do is install your own SSH daemon and run it on a different port, (I use 2223) and use the port-forwarding feature in the host OS, given above. This does something for ChromeOS to start the container and is an SFTP-only server. There is already an SSH daemon running on port 2222.

It can now forward ports, but only to non-privileged port numbers (1024 and above). There have been some changes to the Linux container.
