1 min read

Coding on Chromebooks

Google has added options to set up a virtualized Linux development environment based on Debian. It takes less than 5 minutes to get it up and running with VS Code. Here is a quick walk-through.


Turning on the Development Environment

  1. Enable in Settings

    Enable Linux Env
  2. Follow the Wizard

    wizard 1

    wizard 2blue

    wizard 3


Installing VS Code or Other IDE

You can download a Debian package from code.visualstudio.com

Screenshot 2022-08-12 9.28.22 AM

Adding Other Packages

After this you have a “penguin” container setup with VS Code, Git, and Python3. If you want to do web development you can quickly update your apt-get and install npm or other package managers:

sudo apt-get update && sudo apt-get dist-upgrade

sudo apt-get install npm



That’s it you’re now off to the races and are likely able to work on any number of code projects.

As ChromeOS and the hardware on Chrome devices has matured they are starting to look more attractive as a lightweight Linux-based dev environment.

You can get many high-quality Chromebooks today with good screen resolutions, responsive keyboards and trackpads, and powerful processor/memory specifications. At a fraction of the cost of a typical Windows or Mac-based dev environment, you’re probably wondering “What’s the catch?”

  • Here are the current limitations:
  • Cameras aren't yet supported.
  • Android devices are supported over USB, but other devices aren't yet supported.
  • Android Emulators aren't yet supported.
  • Hardware acceleration isn't yet supported, including GPU and video decode.
  • ChromeVox is supported for the default Terminal app, but not yet for other Linux apps.

What about security? Since these run in an isolated environment your main OS is still protected by secure boot. The backup/restore of the container is the user’s responsibility. Similar to other development environments, where developers have elevated privileges if they run arbitrary code anything in that environment could be accessed i.e. hardcoded usernames/passwords. 

I recommend taking a look at this as an option for some developers on your team. Especially if their work is mainly focused on cloud/web development. If they need access to GPUs or are building mobile apps then a traditional setup is what they’ll need.


New call-to-action

Related Articles

Our Quest for Continuous Delivery

4 min read

Our Quest for Continuous Delivery

The Promevo Engineering team is leveling up! Follow along as we chronicle our journey to achieving Continuous Delivery! In this article, we set the...

Read More
5 Benefits of Using Promevo as Your ChromeOS Provider

3 min read

5 Benefits of Using Promevo as Your ChromeOS Provider

In today's fast-paced business world, staying ahead of the curve is essential. One way to do this is by leveraging the power of ChromeOS devices. ...

Read More
Promevo at Google Cloud Next 2024: A Recap

5 min read

Promevo at Google Cloud Next 2024: A Recap

The glitz and glamor of Las Vegas weren’t the only attractions drawing tech enthusiasts to the Strip this year. Google Cloud Next 2024 took center...

Read More