Can’t open your Project Crostini container Terminal? Here’s how to get access

Lo and behold, I made an unintended mistake today and lost the ability to use the Terminal for Linux apps on my Pixelbook. It turns out that you can manually update the Linux container component by typing chrome://components in your browser bar and selecting the Update option for the cros-termina component.

Chrome components

Just because you can do something doesn’t mean you should. As I, and several others on Reddit found out, the latest version of cros-termina sort of breaks the ability to run the Terminal app on a Chromebook. When I click the Terminal app to open it, it appears and then disappears. Fret not because there’s a solution. And to be honest, the Chromium team is already working on a fix.

Until that happens, following these steps will get you back into your Linux apps on Chrome OS, which of course is only in the Dev Channel for now.

  1. Press ctrl+alt+t to open the standard crosh shell in a browser tab.
  2. Type vsh <vm_name>, where vm_name is very likely termina by default.
  3. Type  lxc exec <container_name> — /bin/login -f <username>. The default container_name should be penguin and the username is whatever user name you used to set up your container in the first place. For me that was kctofel.

What should happen — or at least what happens for me — is the container opens, but not in the Terminal app. Instead you’ll see the Linux environment in crosh, however, it works the same as in Terminal.

Crostini terminal in crosh

It’s likely we won’t need this workaround for long, but I wrote it up because if there’s ever a future occurrence of this issue, I suspect this same workaround will do the trick.

4 thoughts on “Can’t open your Project Crostini container Terminal? Here’s how to get access

  • November 10, 2018 at 3:33 pm
    Permalink

    Man, thanks — opening the Linux terminal has been hit and miss on my Chromebook, with it taking an awkwardly long time to open, or the icon just “spinning and spinning” and not actually opening. This method of yours is fast and so far 100% reliable. Wonderful, thanks!

    Reply
    • November 10, 2018 at 4:52 pm
      Permalink

      ??

      Reply
  • February 26, 2019 at 3:38 pm
    Permalink

    Thanks for this, latest update breaks Terminal as well. Unfortunately, that command just waits for a second, then goes back to the normal `termina` prompt. Any ideas how to debug? I’ve been using `lxc exec penguin /bin/bash`, but that drops me in as root and `su – username`-ing doesn’t allow me to enter a password when I run `sudo` commands. Any idea how I can dig in more deeply?

    Reply
    • May 31, 2019 at 9:55 am
      Permalink

      You can login as root and set/reset your user’s password using `passwd YOURUSERNAME` and then use the instructions above (the -f didn’t work for me) and supply the password you set to get logged in. I prefer working without a password, but to investigate fully why it broke I’m OK with temporarily setting it before I reset everything again.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: