* Quick Review
* Create Container
* Manage Container
* Create Network
* Create Volume
* Remove/Pull Images
* Log/Inspect
apt install git npm nodejs -y
npm install
npm start
In Quick Review service you can see all basic information of all the process running over the docker container. Here you can see following things in form of table.
- List of all Running container
- List of all Existing container
- Docker Volumes list
- Docker Images information
- Docker Network list
Creating a Docker container is a straightforward process that involves specifying the image to use, any required environment variables, and any desired network and volume settings. The following command can be used to launch a Docker container:
docker run [OPTIONS] IMAGE [COMMAND] [ARG...]
In this command, OPTIONS represents any desired options for configuring the container, such as network settings, volume mounts, or port mappings. IMAGE represents the Docker image to use for the container, and COMMAND and ARG... represent any optional commands or arguments to pass to the container.
Some common options that can be passed to the docker run command include:
-p to map a container port to a host port
-e to set environment variables
-v to mount a volume
--network to specify the network to use for the container
This service is help us to launch the docker container over the Docker. You just need to put container name, container image and container image version you want to use over the Docker. You can also put container port, volume name and volume attachment path but these are optional.
This service manages following stuffs like starting, creating, deleting, stopping, restarting and also shows the container logs if terms of debugging anything in the container. You just have to put the container name and then select the action which you want to perform.
In Docker, a network is a virtual network that provides a communication mechanism between containers. Containers can be connected to one or more networks, allowing them to communicate with other containers and/or the host system. Using Docker networks offers several benefits:
Isolation: Docker networks provide a level of isolation between containers, allowing them to communicate securely without exposing their services to the host system or other containers.
Flexibility: Docker networks can be customized to meet the specific needs of an application, such as configuring IP addresses, subnet masks, and other network settings.
Scalability: Docker networks can be used to create complex network topologies that can scale to meet the needs of large, distributed applications.
Security: Docker networks can be used to secure communications between containers by enforcing network policies, such as restricting access to specific ports or IP addresses.
This service provides facilities like creating and deleting the network of the Docker container. Some default network is already there in Docker like bridge and host. If you launch any container by default Docker, put it into the bridge network hence container has connectivity between them. It is very helpful in world of microservices.
In Docker, a volume is a persistent data storage mechanism that allows data to be stored outside of a container's filesystem. A Docker volume is a directory on the host system or within another container that is mounted into a container. Using volumes in Docker offers several benefits:
Data persistence: Containers are ephemeral by design, meaning that any data stored inside a container is lost when the container is stopped or deleted. Volumes allow data to be persisted beyond the lifecycle of a container, ensuring that important data is not lost.
Sharing data between containers: Volumes can be shared between containers, allowing data to be easily transferred from one container to another.
Access to external data: Volumes can be used to access data from outside the Docker environment, such as files on the host system or network-attached storage.
Improved performance: Volumes can be used to store data that is frequently accessed by multiple containers, improving performance by reducing the need to transfer data over the network.
Creating a volume in Docker is a straightforward process. Volumes can be created using the docker volume create command or created automatically when a container is started with a specified volume mount point.
This service provides the facilities to create/delete volume. Make sure volume is not attached to any container before deleting it.
Docker is a popular containerization platform used to develop, package, and deploy applications. Docker images are pre-built packages that contain everything needed to run an application, including the application code, system tools, libraries, and dependencies. While Docker images are essential for building and deploying applications, they can also take up a significant amount of disk space on your system.
Removing or pulling Docker images is the process of deleting or downloading Docker images from a Docker registry or local machine. Here are some of the benefits of removing or pulling Docker images:
Freeing up disk space: By removing unused Docker images, you can free up disk space on your system, which can help improve performance.
Reducing security risks: Old and unused Docker images can become a security risk if they contain vulnerabilities or outdated dependencies. By removing these images, you can reduce the risk of security breaches.
Saving bandwidth: Pulling Docker images from a remote registry can consume a significant amount of bandwidth, especially for large images. By pulling only the necessary images, you can save bandwidth and reduce download times.
Sources for removing or pulling Docker images include:
Docker CLI: The Docker command-line interface (CLI) provides a simple and straightforward way to remove or pull Docker images. You can use the "docker rmi" command to remove images and "docker pull" command to pull images.
Docker Hub: Docker Hub is a central registry for Docker images. You can use Docker Hub to search for and download Docker images. You can also use Docker Hub to delete images that you have pushed to the registry.
Docker API: The Docker API provides a programmatic way to interact with Docker. You can use the API to automate the process of removing or pulling Docker images in your applications and scripts.
Removing or pulling Docker images can help free up disk space, reduce security risks, and save bandwidth. There are various sources for removing or pulling Docker images, including the Docker CLI, Docker Hub, and the Docker API.
To view the description of a Docker container, you can use the docker inspect command. This command provides detailed information about a container, including its configuration, network settings, and more.
To inspect a running Docker container, open a terminal or command prompt and run the following command:
docker inspect <container-id>
Replace with the ID or name of the container you want to inspect. If you don't know the ID or name of the container, you can use the docker ps command to list all running containers and their IDs. Once you run the docker inspect command, you'll see a large JSON object containing all the details about the container. You can use this information to troubleshoot issues, debug your application, or simply understand how your container is configured.
If you want to inspect a stopped container, you can use the docker inspect command with the --format option to specify a format for the output. For example:
docker inspect --format='{{json .State}}' <container-id>
This command will output the container's state information in JSON format, which you can then inspect using a tool like jq. The docker logs command allows you to view the logs of a Docker container. When you run a container, Docker automatically streams the container's output to a log file, which you can then view using the docker logs command.
To view the logs of a running Docker container, open a terminal or command prompt and run the following command:
docker logs <container-id>
Replace with the ID or name of the container you want to view the logs for. By default, this command will show you the logs since the container was started.
Backend folder contains the Code for Docker backend API. Make sure you have put the correct IP address in main.py file before running Flask API. routes directory contains all the basic services which is provided through the API.
| Software | Version |
|---|---|
| Ubuntu | 22.04 |
| Docker Version | 1.13.1 |
| Python Version | 2.7.5 |
| pip3 Version | pip 9.0.3 from /usr/lib/python3.6/site-packages (python 3.6) |
[docker]
baseurl = https://download.docker.com/linux/centos/7/x86_64/stable/
gpgcheck=0
apt install python3 git pip vim docker.io -y
systemctl start docker
systemctl enable docker
sudo pip3 install flask Flask-CORS docker flask-restful
- https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-20-04
- https://www.digitalocean.com/community/questions/nginx-as-a-reverse-proxy-on-port-3000-fails
This is for applying encryption in Docker GUI application. This requires the Ubuntu OS (latest ).
apt update -y
sudo apt install certbot python3-certbot-nginx -y
sudo vim /etc/nginx/sites-available/satyamkumar.tech
<<
server_name satyamkumar.tech www.satyamkumar.tech;
sudo nginx -t
sudo systemctl reload nginx
sudo certbot --nginx -d satyamkumar.tech -d www.satyamkumar.tech
docker build -t satyam0786/dockergui:latest .
docker run --restart=always -dit -p 3000:3000 --name dockergui satyam0786/dockergui:latest
to know more refer this - https://www.digitalocean.com/community/questions/nginx-as-a-reverse-proxy-on-port-3000-fails
location / {
proxy_pass http://65.1.91.102:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location /api {
proxy_pass http://65.1.91.102:5000/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}