Skip to content

Commit b4fe069

Browse files
authored
# edits podman-nextcloud (#1369)
* change to sentence style capitalization on headings * change out contractions * minor changes to wording
1 parent 3c881bb commit b4fe069

File tree

1 file changed

+36
-36
lines changed

1 file changed

+36
-36
lines changed

docs/guides/containers/podman-nextcloud.md

Lines changed: 36 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -12,83 +12,83 @@ tags:
1212

1313
## Introduction
1414

15-
This document explains all the required steps needed to build and run a [Nextcloud](https://nextcloud.com) instance as a Podman container on Rocky Linux. What's more, this entire guide was tested on a Raspberry Pi, so it should be compatible with every Rocky-supported processor architecture.
15+
This document explains all the required steps needed to build and run a [Nextcloud](https://nextcloud.com) instance as a Podman container on Rocky Linux. What is more, this entire guide was tested on a Raspberry Pi, so it should be compatible with every Rocky-supported processor architecture.
1616

1717
The procedure is broken down into multiple steps, each with its own shell scripts for automation:
1818

1919
1. Installing the `podman` and `buildah` packages to manage and build our containers, respectively
20-
2. Creating a base image which will be repurposed for all of the containers we'll need
20+
2. Creating a base image that will be repurposed for all of the containers we will need
2121
3. Creating a `db-tools` container image with the required shell scripts for building and running your MariaDB database
2222
4. Creating and running MariaDB as a Podman container
2323
5. Creating and running Nextcloud as a Podman container, using the MariaDB Podman container as backend
2424

25-
You could run most of the commands in the guide manually, but setting up a few bash scripts will make your life a lot easier, especially when you want to repeat these steps with different settings, variables, or container names.
25+
You could run most of the commands in the guide manually, but setting up a few bash scripts will make your life much easier, especially when you want to repeat these steps with different settings, variables, or container names.
2626

2727
!!! Note "Note for Beginners:"
2828

29-
Podman is tool for managing containers, specifically OCI (Open Containers Initiative) containers. It's designed to be pretty much Docker-compatible, in that most if not all of the same commands will work for both tools. If "Docker" means nothing to you—or even if you're just curious—you can read more about Podman and how it works on [Podman's own website](https://podman.io).
29+
Podman is a tool for managing containers, specifically OCI (Open Containers Initiative) containers. It is designed to be pretty much Docker-compatible, in that most if not all of the same commands will work for both tools. If "Docker" means nothing to you—or even if you were just curious—you can read more about Podman and how it works on [Podman's own website](https://podman.io).
3030

3131
`buildah` is a tool that builds Podman container images based on "DockerFiles".
3232

3333
This guide was designed as an exercise to help people get familiar with running Podman containers in general, and on Rocky Linux specifically.
3434

35-
## Prerequisites and Assumptions
35+
## Prerequisites and assumptions
3636

37-
Here's everything you'll need, or need to know, in order to make this guide work:
37+
Here is everything you will need, or need to know, to make this guide work:
3838

3939
* Familiarity with the command line, bash scripts, and editing Linux configuration files.
4040
* SSH access if working on a remote machine.
41-
* A command-line based text editor of your choice. We'll be using `vi` for this guide.
41+
* A command-line based text editor of your choice. We will be using `vi` for this guide.
4242
* An internet-connected Rocky Linux machine (again, a Raspberry Pi will work nicely).
43-
* Many of these commands must be run as root, so you'll need a root or sudo-capable user on the machine.
43+
* Many of these commands must be run as root, so you will need a root or sudo-capable user on the machine.
4444
* Familiarity with web servers and MariaDB would definitely help.
4545
* Familiarity with containers and maybe Docker would be a *definite* plus, but is not strictly essential.
4646

4747
## Step 01: Install `podman` and `buildah`
4848

49-
First, make sure your system is up-to-date:
49+
First, ensure your system is up-to-date:
5050

5151
```bash
5252
dnf update
5353
```
5454

55-
Then you'll want to install the `epel-release` repository for all the extra packages we'll be using.
55+
Then you will want to install the `epel-release` repository for all the extra packages we will be using.
5656

5757
```bash
5858
dnf -y install epel-release
5959
```
6060

61-
Once that's done, you can update again (which sometimes helps) or just go ahead and install the packages we need:
61+
Once that is done, you can update again (which sometimes helps) or just go ahead and install the packages we need:
6262

6363
```bash
6464
dnf -y install podman buildah
6565
```
6666

67-
Once they're installed, run `podman --version` and `buildah --version` to make sure everything is working correctly.
67+
Once they are installed, run `podman --version` and `buildah --version` to ensure everything is working correctly.
6868

69-
To access Red Hat's registry for downloading container images, you'll need to run:
69+
To access Red Hat's registry for downloading container images, you will need to run:
7070

7171
```bash
7272
vi /etc/containers/registries.conf
7373
```
7474

75-
Find the section that looks like what you see below. If it's commented out, uncomment it.
75+
Find the section that looks like what you see below. If it is commented out, uncomment it.
7676

7777
```
7878
[registries.insecure]
7979
registries = ['registry.access.redhat.com', 'registry.redhat.io', 'docker.io']
8080
insecure = true
8181
```
8282

83-
## Step 02: Create the `base` Container Image
83+
## Step 02: Create the `base` container image
8484

85-
In this guide, we're working as the root user, but you can do this in any home directory. Change to the root directory if you're not already there:
85+
In this guide, we are working as the root user, but you can do this in any home directory. Change to the root directory if you are not already there:
8686

8787
```bash
8888
cd /root
8989
```
9090

91-
Now make all of the directories you'll need for your various container builds:
91+
Now make all of the directories you will need for your various container builds:
9292

9393
```bash
9494
mkdir base db-tools mariadb nextcloud
@@ -156,18 +156,18 @@ And run it:
156156
./build.sh
157157
```
158158

159-
Wait until it's done, and move on to the next step.
159+
Wait until it is done, and move on to the next step.
160160

161-
## Step 03: Create the `db-tools` Container Image
161+
## Step 03: Create the `db-tools` container image
162162

163-
For the purposes of this guide, we're keeping the database setup as simple as we can. You'll want to keep track of the following, and modify them as needed:
163+
For the purposes of this guide, we are keeping the database setup as simple as we can. You will want to keep track of the following, and modify them as needed:
164164

165165
* Database name: ncdb
166166
* Database user: nc-user
167167
* Database pass: nc-pass
168-
* Your server IP address (we'll be using an example IP below)
168+
* Your server IP address (we will be using an example IP below)
169169

170-
First, change to the folder where you'll be building the db-tools image:
170+
First, change to the folder where you will be building the db-tools image:
171171

172172
```bash
173173
cd /root/db-tools
@@ -206,7 +206,7 @@ flush privileges;
206206
eof
207207
```
208208

209-
Lastly, let's setup the DockerFile for the `db-tools` image:
209+
Lastly, setup the DockerFile for the `db-tools` image:
210210

211211
```bash
212212
vi Dockerfile
@@ -228,7 +228,7 @@ And last but not least, create the bash script to build your image on command:
228228
vi build.sh
229229
```
230230

231-
The code you'll want:
231+
The code you will want:
232232

233233
```
234234
#!/bin/bash
@@ -252,7 +252,7 @@ And run it:
252252

253253
## Step 04: Create the MariaDB container image
254254

255-
You're getting the hang of the process, right? It's time to build that actual database container. Change the working directory to `/root/mariadb`:
255+
You are getting the hang of the process, right? It is time to build that actual database container. Change the working directory to `/root/mariadb`:
256256

257257
```bash
258258
cd /root/mariadb
@@ -264,7 +264,7 @@ Make a script to (re)build the container whenever you want:
264264
vi db-init.sh
265265
```
266266

267-
And here's the code you'll need:
267+
And here is the code you will need:
268268

269269
!!! warning
270270

@@ -293,13 +293,13 @@ echo "Listing podman volumes...."
293293
podman volume ls
294294
```
295295

296-
Here's where you make a script to reset your database whenever you like:
296+
Here is where you make a script to reset your database whenever you like:
297297

298298
```bash
299299
vi db-reset.sh
300300
```
301301

302-
And here's the code:
302+
And here is the code:
303303

304304
```
305305
#!/bin/bash
@@ -313,7 +313,7 @@ echo "Creating ncdb Database for nextcloud ....."
313313
podman run --rm --net host db-tools /root/db-create.sh ;
314314
```
315315

316-
And lastly, here's your build script that'll put the whole mariadb container together:
316+
And lastly, here is your build script that will put the whole mariadb container together:
317317

318318
```bash
319319
vi build.sh
@@ -343,9 +343,9 @@ chmod +x *.sh
343343
./build.sh
344344
```
345345

346-
## Step 05: Build and Run the Nextcloud Container
346+
## Step 05: Build and run the Nextcloud container
347347

348-
We're at the final step, and the process pretty much repeats itself. Change to the Nextcloud image directory:
348+
We are at the final step, and the process pretty much repeats itself. Change to the Nextcloud image directory:
349349

350350
```bash
351351
cd /root/nextcloud
@@ -367,7 +367,7 @@ And paste in this bit:
367367
FROM arm64v8/nextcloud
368368
```
369369

370-
Npw create your build script:
370+
Now create your build script:
371371

372372
```bash
373373
vi build.sh
@@ -383,19 +383,19 @@ buildah bud --no-cache -t nextcloud . ;
383383
buildah images -a
384384
```
385385

386-
Now, we're going to set up a bunch of local folders on the host server (*not* in any Podman container), so that we can rebuild our containers and databases without fear of losing all of our files:
386+
Now, we are going to set up a bunch of local folders on the host server (*not* in any Podman container), so that we can rebuild our containers and databases without fear of losing all of our files:
387387

388388
```bash
389389
mkdir -p /usr/local/nc/nextcloud /usr/local/nc/apps /usr/local/nc/config /usr/local/nc/data
390390
```
391391

392-
Lastly, we're going to create the script that will actually build the Nextcloud container for us:
392+
Lastly, we are going to create the script that will actually build the Nextcloud container for us:
393393

394394
```bash
395395
vi run.sh
396396
```
397397

398-
And here's all the code you need for that. Make sure you change the IP address for `MYSQL_HOST` to the docker container that's running your MariaDB instance.
398+
And here is all the code you need for that. Ensure you change the IP address for `MYSQL_HOST` to the docker container that is running your MariaDB instance.
399399

400400
```
401401
#!/bin/bash
@@ -427,7 +427,7 @@ chmod +x *.sh
427427
./build.sh
428428
```
429429

430-
To make sure all of your images have been built correctly, run `podman images`. You should see a list that looks like this:
430+
To ensure all of your images have been built correctly, run `podman images`. You should see a list that looks like this:
431431

432432
```
433433
REPOSITORY TAG IMAGE ID CREATED SIZE

0 commit comments

Comments
 (0)