You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: multipass/Linux.md
+24-24Lines changed: 24 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,18 +28,18 @@ The easiest way to use Multipass is with the primary instance.
28
28
Linux,
29
29
The primary instance is a Multipass virtual machine that is configured to be useful for generic purposes out of the box.
30
30
31
-
The primary instance automatically mounts the $HOME directory (files in this directory are shared between the host and the instance), and it comes with Multipass’s default specs: 1GB of RAM, 5GB of disk, and 1 CPU.
31
+
The primary instance automatically mounts the $HOME directory (files in this directory are shared between the host and the instance), and it comes with Multipass's default specs: 1GB of RAM, 5GB of disk, and 1 CPU.
32
32
-->
33
33
34
34
From the application launcher, let's start Multipass. In Ubuntu, press the super key and type Multipass, or find Multipass in the Applications panel in the lower left of the desktop.
@@ -75,7 +75,7 @@ To check for new updates run: sudo apt update
75
75
ubuntu@primary:~$
76
76
```
77
77
78
-
Let's test it out! As we just learned, the previous step automatically mounted our $HOME directory in the instance. Let's use this to share data with our instance. More concretely, let’s create a new folder in our $HOME directory called Multipass_Files:
78
+
Let's test it out! As we just learned, the previous step automatically mounted our $HOME directory in the instance. Let's use this to share data with our instance. More concretely, let's create a new folder in our $HOME directory called Multipass_Files:
This instance is great for when we just need a quick Ubuntu VM, but let’s say we want a more customised instance. Multipass has us covered there too!
96
+
This instance is great for when we just need a quick Ubuntu VM, but let's say we want a more customised instance. Multipass has us covered there too!
97
97
98
98
[details = "Optional Exercises"]
99
99
Exercise 1:
@@ -105,7 +105,7 @@ In Multipass, an instance with the name `primary` is privileged. For example, it
105
105
106
106
<ahref="#heading--create-a-customised-instance"><h2id="heading--create-a-customised-instance">Create a customised instance</h3></a>
107
107
108
-
Multipass has a great feature to help us get started creating customised instances. Let’s open a terminal and run the command `multipass find`. This shows us a list of all of the images we can launch through Multipass currently.
108
+
Multipass has a great feature to help us get started creating customised instances. Let's open a terminal and run the command `multipass find`. This shows us a list of all of the images we can launch through Multipass currently.
109
109
110
110
```plain
111
111
$ multipass find
@@ -135,9 +135,9 @@ jellyfin latest Jellyfin is a Fre
135
135
minikube latest minikube is local Kubernetes
136
136
```
137
137
138
-
Let’s launch an instance running Ubuntu 22.10 (“Kinetic Kudu”) by typing the command `multipass launch kinetic`
138
+
Let's launch an instance running Ubuntu 22.10 ("Kinetic Kudu") by typing the command `multipass launch kinetic`
139
139
140
-
Now we have an instance running which has been named randomly by Multipass, in my case it is called coherent-trumpetfish.
140
+
Now we have an instance running which has been named randomly by Multipass, in my case it is called "coherent-trumpetfish".
141
141
142
142
```plain
143
143
$ multipass launch kinetic
@@ -148,7 +148,7 @@ We can check some basic info about our new instance by running the following:
This tells multipass to execute the command `lsb_release -a` on the “coherent-trumpetfish” instance.
151
+
This tells multipass to execute the command `lsb_release -a` on the "coherent-trumpetfish" instance.
152
152
153
153
```plain
154
154
$ multipass exec coherent-trumpetfish -- lsb_release -a
@@ -159,17 +159,17 @@ Release: 22.10
159
159
Codename: kinetic
160
160
```
161
161
162
-
Perhaps after using this instance for a while, we decide what we really need is the latest LTS version of Ubuntu, with a more informative name and a little more memory and disk. We can delete the coherent-trumpetfish instance by running
162
+
Perhaps after using this instance for a while, we decide what we really need is the latest LTS version of Ubuntu, with a more informative name and a little more memory and disk. We can delete the "coherent-trumpetfish" instance by running
163
163
164
164
`multipass delete coherent-trumpetfish`
165
165
166
-
Let’s now launch the type of instance we’re looking for by running this:
166
+
Let's now launch the type of instance we're looking for by running this:
We have two instances currently running, the primary instance and our LTS machine with customised specs. Our coherent-trumpetfish instance is still listed, but its state is “Deleted”. We can recover this instance by running `multipass recover coherent-trumpetfish`, but for right now let’s delete the instance permanently by running `multipass purge`. Running `multipass list` again confirms the instance is now permanently deleted:
198
+
We have two instances currently running, the primary instance and our LTS machine with customised specs. Our "coherent-trumpetfish" instance is still listed, but its state is "Deleted". We can recover this instance by running `multipass recover coherent-trumpetfish`, but for right now let's delete the instance permanently by running `multipass purge`. Running `multipass list` again confirms the instance is now permanently deleted:
We’ve now seen a few ways to create, customise, and delete an instance. Now let’s put those instances to work!
207
+
We've now seen a few ways to create, customise, and delete an instance. Now let's put those instances to work!
208
208
209
209
<ahref="#heading--put-your-instances-to-use"><h2id="heading--put-your-instances-to-use">Put your instances to use</h2></a>
210
210
211
211
<ahref="#heading--run-a-simple-web-server"><h3id="heading--run-a-simple-web-server">Run a simple web server</h3></a>
212
212
213
-
Let’s go back to that customised LTS instance we created. Take note of its IP address revealed by `multipass list` in the previous step, then run `multipass shell ltsInstance` to open a shell in the instance.
213
+
Let's go back to that customised LTS instance we created. Take note of its IP address revealed by `multipass list` in the previous step, then run `multipass shell ltsInstance` to open a shell in the instance.
214
214
215
215
From the shell, we can now run:
216
216
@@ -220,19 +220,19 @@ sudo apt update
220
220
sudo apt install apache2
221
221
```
222
222
223
-
Now, let’s open a browser and type in the IP address of the instance into the address bar. We should now see the default Apache homepage.
223
+
Now, let's open a browser and type in the IP address of the instance into the address bar. We should now see the default Apache homepage.
Just like that, we’ve got a web server running in a Multipass instance!
227
+
Just like that, we've got a web server running in a Multipass instance!
228
228
229
229
We can use this web server locally for any kind of local development or testing we like. If however, we want to access this web server from the internet (e.g. from a different computer), we need an instance that is exposed to the external network.
230
230
231
231
<ahref="#heading--launch-from-a-blueprint-to-run-docker-containers"><h3id="heading--launch-from-a-blueprint-to-run-docker-containers">Launch from a Blueprint to run Docker containers</h3></a>
232
232
233
233
Some environments require a lot of configuration and setup. Multipass Blueprints are instances with a deep level of customization. The Docker Blueprint, for example, is a pre-configured Docker environment with a Portainer container already running. We can launch an instance using the Docker Blueprint by running `multipass launch docker --name docker-dev`
234
234
235
-
Once that’s finished, let’s run `multipass info docker-dev` to note down the IP of the new instance.
235
+
Once that's finished, let's run `multipass info docker-dev` to note down the IP of the new instance.
236
236
237
237
```plain
238
238
$ multipass launch docker --name docker-dev
@@ -251,15 +251,15 @@ Memory usage: 259.7MiB out of 3.8GiB
251
251
Mounts: --
252
252
```
253
253
254
-
Let’s take the IP address starting with “10” and paste it into our browser, then add a colon and the portainer default port, 9000, like this: 10.115.5.235:9000. This will take us to the Portainer login page, where we can set a username and password.
254
+
Let's take the IP address starting with "10" and paste it into our browser, then add a colon and the portainer default port, 9000, like this: 10.115.5.235:9000. This will take us to the Portainer login page, where we can set a username and password.
Congratulations! You now have the skills you need to use Multipass proficiently. There’s more to learn about Multipass and its capabilities - check out our [how-to guides](https://multipass.run/docs/how-to-guides) for ideas and for help with your project. Our [reference page](https://multipass.run/docs/reference) contains definitions of key concepts, a complete CLI command reference, settings options and more.
272
+
Congratulations! You now have the skills you need to use Multipass proficiently. There's more to learn about Multipass and its capabilities - check out our [how-to guides](https://multipass.run/docs/how-to-guides) for ideas and for help with your project. Our [reference page](https://multipass.run/docs/reference) contains definitions of key concepts, a complete CLI command reference, settings options and more.
273
273
274
-
Let us know what you’re able to get done with Multipass!
274
+
Let us know what you're able to get done with Multipass!
0 commit comments