transfered existing blog into a new hugo project

2025-12-19 22:14:51 -07:00
commit 7486c791c9
24 changed files with 754 additions and 0 deletions
@@ -0,0 +1,31 @@
+---
+title: "Crostini containers"
+slug: crostini-containers
+date: 2019-05-16T20:37:16-06:00
+tags:
+- chromeos
+- crostini
+- containers
+- customization
+draft: false 
+---
+
+Chromeos is pretty awesome as a developement platform now with the integrated linux support. The project is called [Crostini](https://chromium.googlesource.com/chromiumos/docs/+/master/containers_and_vms.md#Crostini). To install you go to chromeos settings -> Linux and enable it. A locked down read-only VM is installed that uses LXD to run containers that have access to persistant storage. The default container is called penguin and runs a debian variation that has been modified by google. I prefer arch and since the containers run on LXD you can pull containers from [linux container image server](https://us.images.linuxcontainers.org/). If your preference is Fedora, Alpine(great for servers), Ubuntu they're all there. To use penguin just open the terminal app. Now let's go about getting an arch container up and running. First we need a crosh terminal, Ctrl-Alt-T. Once crosh is up we need to start the vm, it's called termina:
+
+<!--more-->
+
+	vmc start termina
+
+Once we're in termina we can use lxc directly to see what the status of any available containers are and see what remotes and images are available.
+```bash
+	lxc list
+	lxc remote list
+	lxc image list images:
+```
+
+Now the old way of starting and adding containers was using lxc. The new way is to use vmc or vsh from the crosh prompt. 
+```bash
+	crosh> vmc container termina arch
+	crosh> vsh termina arch
+	crosh> vmc container <vm> <container> [ <image server, full url> <image alias> ]
+```