-
Notifications
You must be signed in to change notification settings - Fork 521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Carpenters on a Chromebook #746
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Developer mode (Linux) on the Chromebook is leaving beta and has become a stable Linux environment and now should be usable in a Carpentries class.
I have been using this as my daily driver for Linux at home now for a couple of years and have had minimal issues with it, less than I have had in the past using WSL, WSL2, MobaXterm, cygwin, and Brew on OSX. Others have also been using it for carpentries as well:
Of note, the steps to copy and paste the URL are no longer needed or the need to install a second browser, it simply just works (see below).
This should not be confused with "Developer mode," which is very evasive as described in issue #164, this is a built-in VM inside a chromebook commonly known as crostini.
There are a number of features that makes it transparent such as built-in proxy for localhost so users can easily view web servers bound to
localhost
, IPv6 support, built-in X11 support, Docker, etc. Even Microsoft Visual Code Studio works without issue like a native application. The only compatibility issues I have had is when trying to run alternative container systems (singularity - it might be able to run but the default install fails, minikube etc) and most of these would have issues on a MacOS or campus cluster HPC system (VM in a VM is not supported).Setup is simple. Just go to the launcher -> setting (gear) -> advanced -> developers -> and in "Linux development environment" click "Turn On". Optionally uses can change their username and increase the allocated size.
After that participants are in a very clean Debian 10 environment that "just works".
For example, for Jupyter you can simply run
This will automatically connect the chromebook browser to localhost and show the Jupyterlab notebook. This all worked well on a $150 machine with 4GB of ram in under 5 min.
And if anything goes wrong user can simply turn disable (delete) Linux and enable it again for a clean environment.
I have taught computing classes for a number years, and recently have had students use them with success.
I would be willing to author a PR if this is agreeable to remove the "not allowed" status of the Chromebook and author any instructions/documentation that may needed.
The text was updated successfully, but these errors were encountered: