Shadowing Practice: Install NetBox with Docker on Ubuntu 24.04/22.04 LTS | Ep. 2 - Learn English Speaking with Video

Still tracking your network inventory in spreadsheets?

In this video, we are fixing that.

I'd walk you through installing Netbox, which is a powerful modern source of truth for your network using Docker on Ubuntu.

This will serve as the single source of truth for our network automation project in this series.

By the end, you'd have a clean scalable alternative to messy spreadsheet and a good foundation ready for automation.

So this is our Netbox interface.

to organize our site, including which regions they are located.

We can have multiple tenants on netbox and we can add our racks, devices, connections, power connections, wireless,

IPAM, VPN, circuit and all of that.

So basically it provides us all that we need to document

our network in a single place there are two ways

that we can install netbox we can go the manual route

where we'll be responsible for installing the various components of netbox

so like the database caching redis and all of that

so the manual route will do it on our own now this is involving

because it gives us that control but because we are starting out we want to get the

then we can focus on our actual automation.

So in this video, we'd use the Docker version.

Pretty simple and straightforward.

The various components are pre -configured and packaged as container images.

All that we need to do is to pull the repo, define the port on which we want Netbox to listen on,

pull the container images, and start the containers.

First, you can see just a couple of steps and we are done.

And because we'd want to log into Netbox, We'd need to create a user.

In our demo today, we'll be installing Netbox using Docker on Ubuntu 24 .04.

I have tested this with Ubuntu 22 .04 so it works on both versions.

Because we are doing this from scratch, there are dependencies that we need on our Ubuntu server.

We need to install Docker and we need Docker Compose.

Just a quick note on Docker Compose.

version of Docker Compose, but the syntax for that would be docker -compose.

Now the newer version is docker space compose.

The newer version is available in the official Docker repository, not the Ubuntu repo.

What that means is that we have to add the official Docker repo, then we can pull this.

So let's get started.

In my case, I would use an EC2 instance that is running the Ubuntu 24 .04 OS.

So let's open the CLI for this.

As you can see the private IP address 172 .31 .4143,

that right here, and we'll assess this using the public IP address.

So the first thing I'll do right out of the way is to add our Docker repository, because that's where we would pull the Docker Compose.

So add the official GPG key for Docker.

Then we can add the docker repository.

I would make all of these commands available to you, in the video description.

Now that we have this out of the way, we would refresh the list of available packages and versions.

So we do sudo update.

So take just a couple of seconds to run.

Once we are done with this, we would proceed to install the latest version of any packages.

So we do CD app upgrade.

Now we have been asked whether we want to continue on, yes or no. We would say yes.

We could have simply passed this ES at the point of running the command.

So it will take a while for this to run

The reason we did both of these is to ensure that our system is up to date,

is secure before installing any new software like Docker.

So 98 % progress.

We are almost there.

In our case, there was a kernel update which will require us to reboot.

Because this is a lab or a demo, we could have proceeded without rebooting.

A word of caution however, if you are doing this in a production environment,

make sure that you are able to reboot the server in case there's running any other services.

it will just take a couple of seconds for this to reboot.

Let's see.

Let's restart our terminal and see if we should put it.

So we've rebooted our next step.

is to proceed with our installation of Docker and Docker Compose.

Okay.

So we installed Docker, now we passed the "yes" to it at the point of running the command.

Thank you.

Now if we had run Docker version before installing this, we would have seen that we wouldn't have Docker installed but now we have Docker. and start.

Now we proceed to install Docker Compose.

Thank you.

you All done. So...

Docker not okay?

Thank you.

Look So we are good.

Next, we want to ensure that when the server reboots, Docker starts automatically and the service also starts immediately.

So we'll say systemctl .com.

Enable Docker.

and start docker if we check the status We should have the Docker service running.

Okay.

What we want to do next is that we want to ensure

that our current user is able to run Docker commands without SIDO.

To do that, we would add a current user to the Docker group.

Now if we had done just this, we'd have to log out and log in or reboot before this takes effect,

but we want this to take effect immediately.

So at this point, we've looked at the dependencies needed.

to Yeah, we've looked at the dependencies needed to pull a repo and get going.

So our next step, we go and clone the NetBox Docker repository.

Thank you. and navigate.

So when we do a list, we see the folder here.

So we navigate into this folder.

And we do list.

There are two key files that we need to pay attention to.

So the first one is docker -compose .yaml.

In this file, we have the services.

You can think of these as the images that you'll be pulling from Docker.

NetBox, we have the database, caching, redis, and all of that.

Then we also need to create a file which defines the port under which NetBox will be available.

Basically the port that NetBox will listen to.

Now this file must be called specifically dash compose dot override dot YAML.

100

If you look at the list of our files, we don't have that file specifically, but we have an example that tells us how that file can look like.

101

So basically, as we see here, we just have the services netbox and we define the port 8000 and would stick to this.

102

What we'll do next is to actually.

103

write to that file So now if we do a list, we have docker -compose .override .yaml.

104

And if we look into this, It has just what we need.

105

Next step would pull our container images with docker -compose -pull.

106

So it will take about a minute.

107

We are pulling NetBox, we are pulling the database

108

and we are pulling Caching as we saw in the Docker Compose .yaml file.

109

Let's give this a minute.

110

and we should be done good.

111

Now that we have pulled the images, if you do, let's say docker, images we have our images but we don't have any

112

containers running our next step is to start our containers the command we'd use would be Docker Compose

113

We can do this.

114

Let me just give some space so this becomes obvious.

115

Thank you.

116

Thank you.

117

When you do this, we have all the logs show on our screen.

118

The other option is that we can run this in a detached mode.

119

With the detached mode, we can now access to the prompt.

120

I will run it in the detached mode then I'll post it to show you how you can actually check their locks, even their life locks as this runs.

121

This process of starting up the containers will take about

122

five minutes to complete but i would want to

123

you know let it go through

124

the process so that we can see how this works look at the logs and

125

if there are any errors we can take note of them

126

at this point you could have actually exited out of this and check the logs but

127

I would want to wait for about two minutes because there is an error message that

128

you would see or may see and I would want to clarify

129

that so that you are not alarmed when you see that so let's just give this a couple of seconds

130

within two minutes we should see this.

131

You can forward it, about a minute ahead if you can't wait.

132

Thank you.

133

Alright, if you see this arrow, this is still running at the backend.

134

The process of bringing up the container images is still running at the backend.

135

And there are some dependencies that are needed.

136

before netbox actually runs.

137

And we saw that here, right?

138

So we said netbox depends on the database and caching and all of that.

139

We can go ahead and check the logs and see what is happening.

140

So if you do Thank you.

141

Docker Compose Logs Thank you.

142

It will show us their logs, but if you want their live logs as and when it happens,

143

We can add the -f We are still in the process of setting up the various components.

144

I said this will take about five minutes to get done, but I would want us to just wait till we see all that is happening.

145

also in case we run into any errors.

146

Now, if you are taking node, of a netbox interface.

147

So you are seeing virtualization, DCIM, then tenancy, IPAM.

148

This sounds familiar, right?

149

When we went here, we saw all of those.

150

tenancy virtualization ipam so basically at the back end it is setting up all of these components BPMs, wireless, tagging.

151

What we expect to see or cue that everything is okay is that the netbox service is running.

152

So at this point we have not seen it so we are still waiting but they used to fully complete Thank you.

153

Alright, so there we have it.

154

We have our Netbox application started.

155

So we are good at this point.

156

So we can come out of this.

157

And now if you go back to our instance, this is the IP address of our instance.

158

and the port we said was 8000.

159

So there we go, we have our netbox installed, we have our interface, but it is asking us of a username and password.

160

We didn't create one.

161

So that would be our last step so we run this command Thank you to create a super user.

162

It would prompt us for the username, their email address and their password.

163

so a username do packets to purpose Email address then you'd enter your very secured password.

164

confirm the password So our super user has been created successfully.

165

So we go back and we enter our user and our password. So there we go.

166

We have a netbox.

167

Instance fully created from scratch.

168

We don't have anything at this point.

169

There are no regions.

170

There are no sites.

171

We don't have any tenants.

172

There are no devices.

173

Nothing at all.

174

In our next video, we'll look at adding some data into Netbox.

175

So our sites, devices, and all of that.

176

If you found this interesting, kindly subscribe to the channel, hit like and the bell icon so you don't miss any videos.

177

Thank you.

What is the Shadowing Technique?

Shadowing is a science-backed language learning technique originally developed for professional interpreter training and popularized by polyglot Dr. Alexander Arguelles. The method is simple but powerful: you listen to native English audio and immediately repeat it out loud — like a shadow following the speaker with just a 1–2 second delay. Unlike passive listening or grammar drills, shadowing forces your brain and mouth muscles to simultaneously process and reproduce real speech patterns. Research shows it significantly improves pronunciation accuracy, intonation, rhythm, connected speech, listening comprehension, and speaking fluency — making it one of the most effective methods for IELTS Speaking preparation and real-world English communication.

Shadowing Practice: Install NetBox with Docker on Ubuntu 24.04/22.04 LTS | Ep. 2 - Learn English Speaking with Video

Context & Background

Top 5 Phrases for Daily Communication

Step-by-step Shadowing Guide

What is the Shadowing Technique?