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
* Improve language in multipass/Linux.md
Did things like: made sentences more concise, aligned writing with canonical documentation guideline by ensuring that words and phrases that should be avoided are avoided - pronouns are used right and consistently - and words are British instead of American, corrected grammatical errros by using words properly (like the word <now>, recommending when it is used as an adverb and when it is not), and re-wrote confusing sentences.
* Made changes to Linux.md
incorporated suggested changes and ensured that new corrections/ideas are consistely implemented
* Improved Windows.md and macOS.md, and fixed new things in Linux.md
Made improvements to Windows.md and macOS.md generally. Then made specific improvements spotted while re-writing those two to Linux.md.
* implement suggested changes
* implement suggested changes not included in the previous commit
Copy file name to clipboardExpand all lines: multipass/Linux.md
+39-35Lines changed: 39 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
nhart | 2023-12-07 11:18:47 UTC | #1
2
2
3
-
Multipass is a flexible, powerful tool that can be used for many purposes. In its simplest form, it can be used to quickly create and destroy Ubuntu VMs (instances) on any host machine. Used to a fuller extent, Multipass is a local mini-cloud on your laptop, allowing the testing and development of multi-instance or container-based cloud applications.
3
+
Multipass is a flexible and powerful tool that can be used for many purposes. In its simplest form, it can be used to quickly create and destroy Ubuntu VMs (instances) on any host machine. When used maximally, Multipass is a local mini-cloud on your laptop, ensuring that you can test and develop multi-instance or container-based cloud applications.
4
4
5
-
This tutorial will give you an understanding of how Multipass works, and the skills you need to use its main features.
5
+
This tutorial will help you understand how Multipass works, and the skills you need to use its main features.
6
6
7
7
8
8
## Contents
@@ -18,8 +18,9 @@ This tutorial will give you an understanding of how Multipass works, and the ski
Multipass is available for Linux, macOs, or Windows. To install it on your OS of choice, please follow the instructions given [here](https://multipass.run/docs/how-to-guides). Note: This tutorial demonstrates use on Linux, specifically Ubuntu, but the experience on any OS should be similar.
21
+
Multipass is available for Linux, macOS and Windows. To install it on the OS of your choice, please follow the instructions given in this [how-to-guides](https://multipass.run/docs/how-to-guides).
22
22
23
+
Note that this tutorial demonstrates how to use Multipass on Linux, specifically Ubuntu, but the experience on any OS should be similar.
23
24
24
25
<ahref="#heading--create-and-use-a-basic-instance"><h2id="heading--create-and-use-a-basic-instance">Create and use a basic instance</h2></a>
25
26
@@ -30,20 +31,21 @@ The primary instance is a Multipass virtual machine that is configured to be use
30
31
31
32
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
33
-->
33
-
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.
34
+
Start Multipass from the application launcher. In Ubuntu, press the super key and type "Multipass", or find Multipass in the Applications panel on the lower left of the desktop.
Clicking this button does many things in the background: it creates a new virtual machine (instance), named `primary`, with 1GB of RAM, 5GB of disk, and 1 CPU; installs the most recent Ubuntu LTS release on that instance; mounts our $HOME directory in the instance; and opens a shell to the instance, announced by the command prompt `ubuntu@primary`. You can see elements of this in the printout below.
46
+
Clicking this button does many things in the background. First, it creates a new virtual machine (instance) named "primary", with 1GB of RAM, 5GB of disk, and 1 CPU. Second, it installs the most recent Ubuntu LTS release on that instance. Third, it mounts your `$HOME` directory in the instance. Last, it opens a shell to the instance, announced by the command prompt `ubuntu@primary`.
47
+
48
+
You can see elements of this in the printout below:
47
49
48
50
```plain
49
51
Launched: primary
@@ -75,11 +77,11 @@ To check for new updates run: sudo apt update
75
77
ubuntu@primary:~$
76
78
```
77
79
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:
80
+
Let's test it out. As you've just learnt, the previous step automatically mounted your `$HOME` directory in the instance. Use this to share data with your instance. More concretely, create a new folder called `Multipass_Files`in your `$HOME` directory.
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!
98
+
This instance is great for when you just need a quick Ubuntu VM, but let's say you want a more customised instance, how can you do that? Multipass has you covered there too.
97
99
98
100
[details = "Optional Exercises"]
99
101
Exercise 1:
100
-
When you clicked on Open Shell just now, what happened in the background was the equivalent of the CLI commands `multipass launch –name primary` followed by `multipass shell`. Open a terminal and try `multipass shell` (if you didn't follow the steps above, you will have to run the `launch` command first).
102
+
When you select Open Shell, what happens in the background is the equivalent of the CLI commands `multipass launch –name primary` followed by `multipass shell`. Open a terminal and try `multipass shell` (if you didn't follow the steps above, you will have to run the `launch` command first).
101
103
102
104
Exercise 2:
103
-
In Multipass, an instance with the name `primary` is privileged. For example, it is the default argument of multipass shell. In two terminal instances, check `multipass shell primary` and `multipass shell`. Both commands should give the same result.
105
+
In Multipass, an instance with the name "primary" is privileged. That is, it serves as the default argument of `multipass shell` among other capabilities. In different terminal instances, check `multipass shell primary` and `multipass shell`. Both commands should give the same result.
104
106
[/details]
105
107
106
108
<ahref="#heading--create-a-customised-instance"><h2id="heading--create-a-customised-instance">Create a customised instance</h3></a>
107
109
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.
110
+
Multipass has a great feature to help you get started with creating customised instances. Open a terminal and run the `multipass find` command. The result shows a list of all images you can currently launch through Multipass.
109
111
110
112
```plain
111
113
$ multipass find
@@ -135,16 +137,16 @@ jellyfin latest Jellyfin is a Fre
135
137
minikube latest minikube is local Kubernetes
136
138
```
137
139
138
-
Let's launch an instance running Ubuntu 22.10 ("Kinetic Kudu") by typing the command `multipass launch kinetic`
140
+
Launch an instance running Ubuntu 22.10 ("Kinetic Kudu") by typing the `multipass launch kinetic` command.
139
141
140
-
Now we have an instance running which has been named randomly by Multipass, in my case it is called "coherent-trumpetfish".
142
+
Now, you have an instance running and it has been named randomly by Multipass. In this case, it has been named "coherent-trumpetfish".
141
143
142
144
```plain
143
145
$ multipass launch kinetic
144
146
Launched: coherent-trumpetfish
145
147
```
146
148
147
-
We can check some basic info about our new instance by running the following:
149
+
You can check some basic info about your new instance by running the following command:
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
164
+
Perhaps after using this instance for a while, you decide that what you really need is the latest LTS version of Ubuntu, with a more informative name and a little more memory and disk. You can delete the "coherent-trumpetfish" instance by running the following command:
163
165
164
166
`multipass delete coherent-trumpetfish`
165
167
166
-
Let's now launch the type of instance we're looking for by running this:
168
+
You can now launch the type of instance you need by running this command:
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:
200
+
The result shows that you have two instances running, the "primary" instance and the LTS machine with customised specs. The "coherent-trumpetfish" instance is still listed, but its state is "Deleted". You can recover this instance by running `multipass recover coherent-trumpetfish`. But for now, delete the instance permanently by running `multipass purge`. Then run `multipass list` again to confirm that the instance has been permanently deleted.
We've now seen a few ways to create, customise, and delete an instance. Now let's put those instances to work!
209
+
You've now seen a few ways to create, customise, and delete an instance. It is time to put those instances to work!
208
210
209
211
<ahref="#heading--put-your-instances-to-use"><h2id="heading--put-your-instances-to-use">Put your instances to use</h2></a>
210
212
213
+
One way to put a Multipass instance to use is by running a local or web server in it.
214
+
211
215
<ahref="#heading--run-a-simple-web-server"><h3id="heading--run-a-simple-web-server">Run a simple web server</h3></a>
212
216
213
-
Let's go back to that customised LTS instance we created. Take note of its IP addressrevealed by `multipass list` in the previous step, then run `multipass shell ltsInstance` to open a shell in the instance.
217
+
Return to your customised LTS instance. Take note of its IP address, which was revealed when you ran `multipass list`. Then run `multipass shell ltsInstance` to open a shell in the instance.
214
218
215
-
From the shell, we can now run:
219
+
From the shell, you can run:
216
220
217
221
```
218
222
sudo apt update
219
223
220
224
sudo apt install apache2
221
225
```
222
226
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.
227
+
Open a browser and type in the IP address of your instance into the address bar. You should now see the default Apache homepage.
Just like that, we've got a web server running in a Multipass instance!
231
+
Just like that, you've got a web server running in a Multipass instance!
228
232
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.
233
+
You can use this web server locally for any kind of local development or testing. However, if you want to access this web server from the internet (for instance, a different computer), you need an instance that is exposed to the external network.
230
234
231
235
<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
236
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`
237
+
Some environments require a lot of configuration and setup. Multipass Blueprints are instances with a deep level of customization. For example, the Docker Blueprint is a pre-configured Docker environment with a Portainer container already running. You can launch an instance using the Docker Blueprint by running `multipass launch docker --name docker-dev`.
234
238
235
-
Once that's finished, let's run `multipass info docker-dev` to note down the IP of the new instance.
239
+
Once that's done, run `multipass info docker-dev` to note down the IP of the new instance.
236
240
237
241
```plain
238
242
$ multipass launch docker --name docker-dev
@@ -251,25 +255,25 @@ Memory usage: 259.7MiB out of 3.8GiB
251
255
Mounts: --
252
256
```
253
257
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.
258
+
Copy the IP address starting with "10" and paste it into your browser, then add a colon and the portainer default port, 9000. It should look like this: 10.115.5.235:9000. This will take you to the Portainer login page where you can set a username and password.
From the Portainer dashboard, we can see the ports that nginx has available. We can navigate to the IP address of our instance followed by that port number to see that we indeed have nginx running in a docker container inside Multipass!
270
+
From the Portainer dashboard, you can see the ports available on nginx. To verify that you have nginx running in a Docker container inside Multipass, open a new web page and paste the IP address of your instance followed by one of the port numbers.
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.
276
+
Congratulations! You can now 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 help with your project. Our [reference pages](https://multipass.run/docs/reference)contain definitions of key concepts, a complete CLI command reference, settings options and more.
273
277
274
278
Let us know what you're able to get done with Multipass!
0 commit comments