Cloud servers from $4/mo - Grab the Deal! Let’s start ->
Running Selenium with Chrome in Docker
Docker
19.06.2025
Reading time: 5 min
Share
Sometimes, it’s useful to work with Selenium in Python within a Docker container. This raises questions about the benefits of using such tools, version compatibility between ChromeDriver and Chromium, and the nuances of their implementation. In this article, we’ll cover key considerations and provide solutions to common issues.
Why Run Selenium in Docker?
Running Selenium in a container offers several advantages:
- Portability: Easily transfer the environment between different machines, avoiding version conflicts and OS-specific dependencies.
- Isolation: The Selenium container can be quickly replaced or updated without affecting other components on the server.
- CI/CD Compatibility: Dockerized Selenium fits well into CI/CD pipelines — you can spin up a clean test environment from scratch each time your system needs testing.
Preparing an Ubuntu Server for Selenium with Docker
First, make sure Docker and Docker Compose are installed on the server:
docker --version && docker compose versionIn some Docker Compose versions, the command is docker-compose instead of docker compose.
If the tools are installed, you’ll see output confirming their versions. If not, follow this guide.
Selenium in Docker Example
When deploying Selenium in Docker containers, consider the host architecture, functional requirements, and performance. Official selenium/standalone-* images are designed for AMD64 (x86_64) CPUs, while seleniarm/standalone-* images are adapted for ARM architectures (e.g., Apple silicon or ARM64 server CPUs).
First, create a docker-compose.yml file in your project root. It will contain two services:
version: "3"
services:
app:
build: .
restart: always
volumes:
- .:/app
depends_on:
- selenium
platform: linux/amd64
selenium:
image: selenium/standalone-chromium:latest # For AMD64
# image: seleniarm/standalone-chromium:latest # For ARM64
container_name: selenium-container
restart: unless-stopped
shm_size: 2g
ports:
- "4444:4444" # Selenium WebDriver API
- "7900:7900" # VNC Viewer
environment:
- SE_NODE_MAX_SESSIONS=1
- SE_NODE_OVERRIDE_MAX_SESSIONS=true
- SE_NODE_SESSION_TIMEOUT=300
- SE_NODE_GRID_URL=http://localhost:4444
- SE_NODE_DETECT_DRIVERS=false
You must choose the correct image for your system architecture by uncommenting the appropriate line.
The app service will run your main Python code. Let’s define a standard Dockerfile for this service:
# Use a minimal Python image
FROM python:3.11-slim
# Set working directory
WORKDIR /app
# Install Python dependencies
COPY requirements.txt /app/
RUN pip install --no-cache-dir -r requirements.txt
# Copy project files
COPY . /app/
# Set environment variables (Chromium is in a separate container)
ENV SELENIUM_REMOTE_URL="http://selenium:4444/wd/hub"
# Run Python script
CMD ["python", "main.py"]
This Dockerfile uses a base Python image and automatically installs the necessary dependencies.
Now let’s add the driver initialization script to main.py:
import time # Used to create a delay for checking browser functionality
import os
from selenium import webdriver
from selenium.webdriver.chrome.service import Service
from selenium.webdriver.chrome.options import Options
# WebDriver settings
chrome_options = Options()
chrome_options.add_argument("--no-sandbox")
chrome_options.add_argument("--disable-dev-shm-usage")
chrome_options.add_argument("--disable-gpu")
chrome_options.add_argument("--disable-webrtc")
chrome_options.add_argument("--hide-scrollbars")
chrome_options.add_argument("--disable-notifications")
chrome_options.add_argument("--start-maximized")
SELENIUM_REMOTE_URL = os.getenv("SELENIUM_REMOTE_URL", "http://selenium:4444/wd/hub")
driver = webdriver.Remote(
command_executor=SELENIUM_REMOTE_URL,
options=chrome_options
)
# Open a test page
driver.get("https://www.timeweb.cloud")
time.sleep(9999)
# Shut down WebDriver
driver.quit()
In the requirements.txt file, list standard dependencies, including Selenium:
attrs==25.1.0
certifi==2025.1.31
h11==0.14.0
idna==3.10
outcome==1.3.0.post0
PySocks==1.7.1
selenium==4.28.1
sniffio==1.3.1
sortedcontainers==2.4.0
trio==0.28.0
trio-websocket==0.11.1
typing_extensions==4.12.2
urllib3==2.3.0
websocket-client==1.8.0
wsproto==1.2.0
Now you can launch the containers:
docker compose up -dExpected output: Docker will build and launch the containers.
To verify everything is running correctly:
docker compose psYou should see two running containers which means everything was loaded successfully. You can now integrate a script in main.py to interact with any site.
Debugging Selenium in Docker with VNC
In official Selenium Docker images (like seleniarm/standalone-chromium, selenium/standalone-chrome, etc.), direct access to the Chrome DevTools Protocol is usually overridden by Selenium Grid. It generates a new port for each session and proxies it via WebSocket.
Arguments like --remote-debugging-port=9229 are ignored or overwritten by Selenium, making direct browser port access impossible from outside the container.
Instead, these Docker images offer built-in VNC (Virtual Network Computing), similar to TeamViewer or AnyDesk, but working differently.
VNC requires headless mode to be disabled, since it transmits the actual screen content — and if the screen is blank, there will be nothing to see.
You can connect to the VNC web interface at:
http://<server_ip>:7900When connecting, you'll be asked for a password. To generate one, connect to the selenium-container via terminal:
docker exec -it selenium-container bashThen enter:
x11vnc -storepasswdYou’ll be prompted to enter and confirm a password interactively.
Enter the created password into the VNC web interface, and you’ll gain access to the browser controlled by Selenium inside Docker.
From there, you can open DevTools to inspect DOM elements or debug network requests.
Conclusion
Running Selenium in Docker containers simplifies environment portability and reduces the risk of version conflicts between tools. It also allows visual debugging of tests via VNC, if needed. Just make sure to choose the correct image for your system architecture and disable headless mode when a graphical interface is required. This provides a more flexible and convenient infrastructure for testing and accelerates Selenium integration into CI/CD pipelines.
Docker
19.06.2025
Reading time: 5 min
Share
Similar
Docker
Building Docker Images and Deploying Applications
Containerizing applications offers a convenient and flexible way to quickly deploy software, including web servers, databases, monitoring systems, and others. Containers are also widely used in microservices architectures. Docker is ideal for these purposes, as it greatly simplifies working with containerized apps. Introduced in 2013, Docker has seen continuous support and usage ever since.
In this tutorial, you’ll learn how to create Docker images for three different applications written in different programming languages and how to run Docker containers from these images.
Prerequisites
To work with the Docker platform, you’ll need:
A VPS or virtual machine with any Linux distribution preinstalled. In this tutorial, we use Ubuntu 22.04.
Docker installed. You can find the Docker installation guide for Ubuntu 22.04 in our tutorials. Alternatively, you can use a prebuilt cloud server image with Docker — just select it in the “Marketplace” tab when creating a server.
What Is a Docker Image?
At the core of Docker’s concept is the image. A Docker image is a template—an executable file—you can use to start a Docker container. It contains everything needed to launch a ready-to-run application: source code, configuration files, third-party software, utilities, and libraries.
Docker image architecture is layer-based. Each layer represents an action performed during the image build process, such as creating files and directories or installing software. Docker uses the OverlayFS file system, which merges multiple mount points into one, resulting in a unified directory structure.
You can move Docker images between systems and use them in multiple locations, much like .exe executables in Windows systems.
Creating Custom Docker Images
Let’s walk through how to create Docker images for Flask, Node.js, and Go applications.
Creating a Docker Image for a Flask Application
To create images, a Dockerfile is used. Dockerfile is a plain text file without an extension that defines the steps to build a container image. You can find more details about Dockerfile instructions in the official documentation.
We’ll create a Docker image with a web application built with Flask and run the container. The application will show a basic HTML page that displays the current date.
1. Install Required Packages
Install the pip package manager and python3-venv for managing virtual environments:
apt -y install python3-pip python3-venv
2. Create the Project Directory
mkdir dockerfile-flask && cd dockerfile-flask
3. Create and Activate a Virtual Environment
python -m venv env
source env/bin/activate
After activation, you'll see (env) in your prompt, indicating the virtual environment is active. Packages installed via pip will now only affect this environment.
4. Install Flask and Dependencies
pip install flask
pip install MarkupSafe==2.1.5
5. Create the Flask Application
Create a file named app.py that will store the source code of our application:
from flask import Flask
import datetime
app = Flask(__name__)
@app.route('/')
def display_current_date():
current_date = datetime.datetime.now().date()
return f"Current date is: {current_date}"
if __name__ == '__main__':
app.run(debug=True)
6. Run and Test the Application
flask run --host=0.0.0.0 --port=80
In your browser, visit your server’s IP address (port 80 doesn’t need to be specified as it’s the default one). You should see today’s date.
7. Freeze Dependencies
Now, we need to save all the dependencies (just the flask package in our case) to a requirements.txt file, which stores all packages used in the project and installed via pip.
pip freeze > requirements.txt
Your project structure should now look like this:
dockerfile-flask/
├── app.py
├── env/
├── requirements.txt
Now we can proceed to creating a Docker image.
8. Create the Dockerfile
Create a file named Dockerfile with the following contents:
FROM python:3.8-slim-buster
WORKDIR /app
COPY requirements.txt requirements.txt
RUN pip3 install -r requirements.txt
COPY . .
CMD [ "python3", "-m", "flask", "run", "--host=0.0.0.0", "--port=80" ]
Explanation:
FROM python:3.8-slim-buster: Use Python 3.8 base image on a lightweight Debian Buster base.
WORKDIR /app: Set the working directory inside the container (similar to the mkdir command in Linux systems)
COPY requirements.txt requirements.txt: Copy the dependency list into the image.
RUN pip3 install -r requirements.txt: The RUN directive runs the commands in the image. In this case, it’s used to install dependencies.
COPY . .: Copy all project files into the container.
CMD [...]: CMD defines the commands and app parameters to be used when the container starts.
9. Use a .dockerignore File
Create a .dockerignore file to exclude unnecessary directories. It helps to decrease the image size.
In our case, we have two directories that we don’t need to launch the app. Add them to the .dockerignore file:
env
__pycache__
10. Build the Docker Image
When building the image, we need to use a tag that would work as an identifier for the image. We’ll use the flask-app:01 tag.
docker build -t flask-app:01 .
The dot at the end means the Dockerfile is located in the same directory where we run the command.
Check the created image:
docker images
11. Run the Docker Container
docker run -d -p 80:80 flask-app:01
-d: Run the container in the background.
-p: Forward host port 80 to container port 80.
Check running containers:
docker ps
The STATUS column should show “Up”.
Open your browser and navigate to your server's IP address to view the app.
Creating a Docker Image for a Node.js Application
Our simple Node.js app will display the message: “This app was created using Node.js!”
Make sure you have Node.js installed on your system.
1. Create the Project Directory
mkdir dockerfile-nodejs && cd dockerfile-nodejs
2. Initialize the Project
npm init --yes
3. Install Express
npm install express --save
4. Create the Application File
Create app.js with the following code:
const express = require("express");
const app = express();
app.get("/", function(req, res) {
return res.send("This app was created using Node.js!");
});
app.listen(3000, '0.0.0.0', function(){
console.log('Listening on port 3000');
});
5. Test the Application
node app.js
Open http://<your-server-ip>:3000 in a browser to verify it works.
6. Create the Dockerfile
FROM node:20
WORKDIR /app
COPY package.json /app
RUN npm install
COPY . /app
CMD ["node", "app.js"]
7. Add .dockerignore
Create .dockerignore and the following line:
**/node_modules/
8. Build the Image
docker build -t nodejs-app:01 .
9. Start the Container from Image
docker run -d -p 80:3000 nodejs-app:01
Visit http://<your-server-ip> in your browser. The app should be running.
Creating a Docker Image for a Go Application
This Go application will display: “Hello from GO!”
Make sure you have Go installed in your system.
1. Create the Project Directory
mkdir dockerfile-go && cd dockerfile-go
2. Initialize the Go Module
go mod init go-test-app
3. Create the Application File
Create main.go with this code of our application:
package main
import "fmt"
func main() {
fmt.Println("Hello from GO!")
}
Verify it works:
go run .
4. Create the Dockerfile
FROM golang:1.23-alpine
WORKDIR /app
COPY go.mod ./
RUN go mod download
COPY *.go ./
RUN go build -o /go-test
CMD [ "/go-test" ]
COPY go.mod ./: Adds dependencies file.
RUN go mod download: Installs dependencies.
COPY *.go ./: Adds source code.
RUN go build -o /go-test: Compiles the binary.
5. Build the Image
docker build -t go:01 .
6. Run the Container
docker run go:01
You should see the output: Hello from GO!
Conclusion
In this guide, we walked through building custom Docker images for three applications written in different programming languages. Docker allows you to package any application and deploy it with ease.
18 June 2025 · 7 min to read
Docker
How to Install Docker on MacOS
Docker is a platform that makes it easier to create, deploy, and operate applications in containers. Containers enable developers to bundle an application's dependencies, including as libraries, frameworks, and runtime environments, and ship it as a single package. This ensures that the program runs reliably and consistently, independent of the environment in which it is deployed. If you have troubles with that, here's our instruction how to deploy server with Docker.
Docker allows you to automate the deployment of software inside lightweight, portable containers. These containers may operate on any system with Docker installed, making it simple to deploy apps across several settings, such as a developer's laptop, a testing server, or a production environment on the cloud. Docker also includes tools for managing and orchestrating containers at scale, making it simpler to deploy, scale, and manage complex applications in production environments.
Below are the requirements to prepare for the installation of docker on MacOS:
A supported version of MacOS. Docker Desktop is compatible with the latest macOS versions. This includes the current macOS release as well as the two previous releases. As new major versions of macOS become widely available, Docker stops supporting the oldest version and instead supports the most recent version (along with the prior two).
RAM: minimum of 4 GB. This is to optimize Docker performance especially when operating multiple containers.
In installing docker, you can either install it interactively or manually or via the command line interface. Here’s the guide on how to do the installation with both methods.
Manual Installation
Download the installer from the official docker website using the following links:
Apple Silicon processor
Intel chip processor
Install Docker Desktop by double-clicking the Docker.dmg:
And drag and drop it to the Application folder.
By default, the Docker Desktop is installed at /Applications/Docker.
Wait for the copying to finish.
Double-click the Docker from the Applications folder to proceed with the installation.
Click Accept to continue in the Docker Subscription Service Agreement page.
From the installation window, choose either:
Use recommended settings (Requires password)
Use advanced settings
Click Finish.
Verify if installation is successful. A Docker icon should appear on the menu bar when the Docker Desktop is installed and running. A notification will appear stating that Docker is running.
Install using Command Line Interface
Once Docker.dmg is downloaded from the official docker website, login as a super user / root in a terminal to install Docker Desktop in the Application folder. Execute the below commands respectively.
hdiutil attach Docker.dmg
/Volumes/Docker/Docker.app/Contents/MacOS/install
hdiutil detach /Volumes/Docker
If running as a normal user, execute the command with sudo:
sudo hdiutil attach Docker.dmg
sudo /Volumes/Docker/Docker.app/Contents/MacOS/install
sudo hdiutil detach /Volumes/Docker
Installation might take some time to complete since the system may do various security checks while installing Docker on Mac.
Troubleshooting
Some of the common issues that the user might encounter during the installation of MacOS are:
Users may not check the MacOs version of their machine. Take note of the system requirements when installing Docker on MacOS to avoid installation failure and unexpected behavior (like docker image becomes corrupted).
Errors during the installation process may occur such as failed downloads, incomplete installation, etc. Go back and check the system and hardware compatibility of the machine.
Conflict with existing software. This requires troubleshooting and investigating system logs. Usually, this can be solved by removing the problematic software.
Permission and security issues. When installing Docker on MacOS, ensure that the machine has all the required permission to access system resources, like directory, network, etc.
Conclusion
To summarize, installing Docker on MacOS provides various opportunities for both developers and system administrators. Docker technology provides resources with an enhanced development workflow, an efficient procedure for delivering apps, and consistent system environments. Embrace containerization to broaden your development horizons.
Check what Hostman VPS Servers can give you.
30 April 2025 · 4 min to read
Docker
Installing and Using Nexus Repository for Artifact Storage
In software development, "artifact" is a component of a developed software product. Artifacts include executable and binary files, software packages, and more.
As the product's architecture and functionality increase, the number of artifacts grows exponentially, and you need a reliable storage solution that can manage large volumes of artifacts efficiently.
One such solution is Nexus Repository by Sonatype.
Nexus supports over 15 artifact formats, including APT, Docker, Go, Helm, Maven, npm, PyPi, and more.
There are two versions of Nexus Repository:
Free version – Includes essential repository management features.
Commercial version – Offers customer support and a broader range of supported artifact types.
In this guide, we will install the free version of Nexus Repository.
Prerequisites
You can install Nexus Repository on a Linux, Windows, or MacOS machine.
In this guide, we will use a Hostman cloud server running Ubuntu.
The server must meet the following minimum requirements:
4-core CPU. 8-core or higher is recommended.
8 GB RAM
50 GB of free disk space (excluding OS and other installed software). If there is insufficient space, Nexus will not start.
The official Sonatype website provides recommended system requirements based on the number of repositories and stored artifacts.
Installing Nexus Repository
Step 1: Install Java
First, update the package list:
sudo apt update
Then, install Java 8 using OpenJDK:
sudo apt -y install openjdk-8-jre-headless
After installation, verify Java's version:
java -version
If you have multiple Java versions installed, switch to Java 8:
sudo update-alternatives --config java
Select the correct version using the TAB key and confirm with Enter.
Step 2: Download and Extract Nexus
We will install Nexus in the /opt directory.
Download the latest Nexus archive:
sudo wget https://download.sonatype.com/nexus/3/latest-unix.tar.gz
Extract the archive to /opt:
sudo tar -zxvf latest-unix.tar.gz -C /opt
Rename the extracted directory (for easier management):
sudo mv /opt/nexus-3.61.0-02 /opt/nexus
Make sure to specify the correct version number in your case.
Step 3: Create a Dedicated User for Nexus
Create a new user named nexus:
sudo adduser nexus
Disable direct login for this user:
sudo usermod nexus -s
Set the correct ownership for Nexus directories:
sudo chown -R nexus:nexus /opt/nexus /opt/sonatype-work
Step 4: Configure Nexus
Edit the Nexus configuration file:
sudo nano /opt/nexus/bin/nexus.rc
Uncomment (remove #) and set the user as nexus:
run_as_user="nexus"
Save and exit the file.
Step 5: Create a Systemd Service for Nexus
Create a new service file:
sudo nano /etc/systemd/system/nexus.service
Add the following content:
[Unit]
Description=Nexus Repository Manager
After=network.target
[Service]
Type=forking
LimitNOFILE=65536
ExecStart=/opt/nexus/bin/nexus start
ExecStop=/opt/nexus/bin/nexus stop
User=nexus
Restart=on-abort
[Install]
WantedBy=multi-user.target
Save and exit the file.
Step 6: Start and Enable Nexus
Start Nexus:
sudo systemctl start nexus
Check Nexus status:
systemctl status nexus
If the status is active, Nexus is running successfully.
Enable Nexus to start on boot:
sudo systemctl enable nexus
Step 7: Verify Nexus Startup
Nexus takes 2-3 minutes to fully start. To check the logs:
tail -f /opt/sonatype-work/nexus3/log/nexus.log
Once you see:
Started Sonatype Nexus OSS
Nexus is ready.
By default, the Nexus web interface is accessible on port 8081:
http://your-server-ip:8081
Initial Setup of Nexus Repository
Step 1: Log into Nexus
Open the Nexus web interface.
Click the Sign in button (top-right corner).
Retrieve the default admin password by running:
cat /opt/sonatype-work/nexus3/admin.password
Use this password to log in as admin.
Step 2: Initial Configuration
Set a new password for the admin user.
Enable or disable anonymous access:
Enabled: Any user with the repository URL can browse/download artifacts without authentication.
Disabled: Authentication (login/password) is required.
Nexus is now ready to use.
Creating a Docker Repository in Nexus
Step 1: Create a Docker Repository
Log in as admin.
Go to Server Administration and Configuration (gear icon).
In the left menu, select Repositories.
Click Create repository.
Choose docker (hosted).
Step 2: Configure the Repository
Nexus supports three types of repositories:
Hosted: Stores artifacts directly in Nexus.
Proxy: Fetches artifacts from remote repositories (e.g., APT).
Group: Combines multiple repositories into one unified endpoint.
For a Docker repository:
Set a repository name, e.g., docker-images.
Enable HTTP access (check the box).
Assign a port number (e.g., 8083).
Save the settings.
Step 3: Configure Docker to Work with Nexus
By default, Docker does not allow HTTP connections. To enable HTTP access:
Edit or create the Docker daemon configuration file:
sudo nano /etc/docker/daemon.json
Add the following configuration:
{
"insecure-registries": ["166.1.227.189:8083"]
}
(Replace 166.1.227.189:8083 with your Nexus server IP and port.)
Save and exit the file.
Restart the Docker service:
sudo systemctl restart docker
Warning: Restarting Docker affects running containers. Containers without the --restart=always flag may not restart automatically.
Step 4: Push a Docker Image to Nexus
Log in to Nexus via Docker:
docker login 166.1.227.189:8083
You can use the admin username and the password you set earlier.
Tag an image (e.g., alpine):
docker tag alpine:latest 166.1.227.189:8083/alpine-test
Verify the new tag:
docker images
Push the image to Nexus:
docker push 166.1.227.189:8083/alpine-test
Confirm the upload:
Open the Nexus web interface.
Go to the docker-images repository.
The alpine-test image should be listed.
Your Nexus repository is now set up for Docker image storage!
HTTPS Configuration
The correct approach when working with Docker repositories is to use the HTTPS protocol. To configure HTTPS in Nexus, follow these steps:
Navigate to the /opt/nexus/etc/ssl directory:
cd /opt/nexus/etc/ssl
Use keytool to generate a self-signed certificate:
sudo keytool -genkeypair -keystore keystore.jks -storepass test12345 -keypass test12345 -alias jetty -keyalg RSA -keysize 2048 -validity 1000 -dname "CN=*.${NEXUS_DOMAIN}, OU=test, O=test1, L=Unspecified, ST=Unspecified, C=RU" -ext "SAN=DNS:nexus-repo.com,IP:166.1.227.189" -ext "BC=ca:true"
Replace the following values with your own:
-keystore keystore.jks — Name of the file where the key will be stored, using the .jks format.
-storepass test12345 — Password for accessing the key store.
-keypass test12345 — Password for accessing the private key.
-ext "SAN=DNS:nexus-repo.com,IP:166.1.227.189" — Specifies your Nexus server's domain name and IP address.
If a local domain is used, it must be added to the /etc/hosts file (for Linux) or C:\Windows\System32\drivers\etc\hosts in Windows.
Next, extract the server certificate from the generated keystore.jks file using the following command:
sudo keytool -export -alias jetty -keystore keystore.jks -rfc -file nexus.cert
The output will be a certificate file named nexus.cert.
Now, edit the Nexus configuration file nexus-default.properties located in /opt/nexus/etc:
sudo nano /opt/nexus/etc/nexus-default.properties
Find the section with the comment # Jetty section, and add the following parameter:
application-port-ssl=8443
This specifies the port where HTTPS will be available.
In the same section, add this line:
nexus-args=${jetty.etc}/jetty.xml,${jetty.etc}/jetty-http.xml,${jetty.etc}/jetty-https.xml,${jetty.etc}/jetty-requestlog.xml
Next, edit the jetty-https.xml file located in /opt/nexus/etc/jetty:
sudo nano /opt/nexus/etc/jetty/jetty-https.xml
Locate the block named sslContextFactory.
In the fields KeyStorePassword, KeyManagerPassword, TrustStorePassword, enter the password used during certificate generation. In this example, the password is test12345.
In the parameters KeyStorePath and TrustStorePath, specify the name of the generated certificate.
After making these changes, restart the Nexus service:
sudo systemctl restart nexus
Installing the Certificate on Linux
In Linux, we must install the certificate at the OS level. Otherwise, when trying to authenticate to the repository using the docker login command, the following error may occur:
x509: certificate signed by unknown authority
To install the certificate on Ubuntu/Debian, follow these steps:
Install the ca-certificates package:
sudo apt -y install ca-certificates
The certificate must be in .crt format, as other formats are not supported. Since the certificate was generated as .cert, rename it to .crt:
sudo mv nexus.cert nexus.crt
Copy the certificate to /usr/local/share/ca-certificates:
sudo cp nexus.crt /usr/local/share/ca-certificates
Install the certificate using the following command:
sudo update-ca-certificates
Configuring HTTPS in the Nexus Repository
To configure HTTPS in the repository:
Open the Nexus web interface and log in as an administrator.
Navigate to the Server Administration and Configuration section (gear icon).
In the left menu, select Repositories, find the required repository, check the box next to HTTPS, and specify a port that is not already in use on the server, such as 8344.
4 Save the changes.
On the server, run the docker login command, specifying the repository address and HTTPS port:
docker login nexus-repo.com:8344
You can log in using the admin account.
Pushing an Image to the Repository
To test pushing an image, let's use nginx:
Assign a tag to the image. The format for Docker image tags is as follows:
image:tag registry_address:repository_port/image_name
Example:
docker tag nginx:latest nexus-repo.com:8344/nginx-test
Verify that the new image exists:
docker images
Push the image to the repository:
docker push nexus-repo.com:8344/nginx-test
Open the Nexus web interface, navigate to the repository, and confirm that the image was successfully uploaded.
Conclusion
Nexus Repository is an excellent solution for storing and managing artifacts. Supporting a wide range of artifact formats, it is suitable for both small development teams and larger enterprises.
11 March 2025 · 8 min to read
Do you have questions,
comments, or concerns?
Our professionals are available to assist you at any moment,
whether you need help or are just unsure of where to start.
whether you need help or are just unsure of where to start.
