服务器 
首页 > 服务器 > 浏览文章

Docker容器简单部署nginx过程解析

(编辑:jimmy 日期: 2024/11/19 浏览:3 次 )

1、容器中部署nginx服务

centos:7镜像运行一个容器,并且,在这个容器内部署Nginx服务。

[root@Docker ~]# docker pull centos:7 //下载镜像
[root@Docker ~]# docker run -itd --name webapp --restart=always centos:7 //运行一个容器名为:webapp
[root@Docker ~]# docker cp nginx-1.16.0.tar.gz webapp:/root //将本地nginx包导入webapp容器内
[root@Docker ~]# docker exec -it webapp /bin/bash //进入容器
[root@85099880dabe ~]# tar zxf nginx-1.16.0.tar.gz
[root@85099880dabe ~]# cd nginx-1.16.0
[root@85099880dabe nginx-1.16.0]# yum install gcc pcre pcre-devel zlib zlib-devel openssl openssl-devel //下载相关依赖包
[root@85099880dabe nginx-1.16.0]# useradd -M -s /sbin/nologin nginx //添加一个没有登录权限的nginx用户
[root@85099880dabe nginx-1.16.0]# ./configure --prefix=/usr/local/nginx --user=nginx --group=nginx //编译安装

Docker容器简单部署nginx过程解析

[root@85099880dabe nginx-1.16.0]# make && make install //编译安装
[root@85099880dabe nginx-1.16.0]# ln -s /usr/local/nginx/sbin/* /usr/local/sbin/ //创建软链接
[root@85099880dabe nginx-1.16.0]# nginx
[root@85099880dabe nginx-1.16.0]# nginx //确认nginx服务开启
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
[root@85099880dabe nginx-1.16.0]# cd /usr/local/nginx/html/
[root@85099880dabe html]# echo "TEST WEB" > index.html
[root@85099880dabe html]# curl 127.0.0.1
TEST WEB

2、迁移镜像

所需环境:

docker1主机:192.168.45.129

docker2主机:192.168.45.134

1)docker1主机

将docker1的刚刚创建的容器并制作成镜像导入docker2主机上

[root@Docker ~]# docker commit webapp myweb //将webapp容器制作成镜像名为myweb
sha256:b035b8e8a36140e1bdbda9cf3a736b139ea8a48db7871a10f509b8f34d4c0f82
[root@Docker ~]# docker save > myweb.tar myweb:latest //将镜像导出
[root@Docker ~]# scp myweb.tar 192.168.45.134:/root //将镜像导出的tar包cp给docker2主机
The authenticity of host '192.168.45.134 (192.168.45.134)' can't be established.
ECDSA key fingerprint is d7:77:71:90:34:25:c0:ec:e0:b6:5c:cc:6b:44:93:7b.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.45.134' (ECDSA) to the list of known hosts.
root@192.168.45.134's password: //密码为docker2主机的密码
myweb.tar 100% 353MB 176.4MB/s 00:02

2)docker2主机

[root@Docker2 ~]# docker load < myweb.tar //将刚刚cp过来的tar包制作成镜像
[root@Docker2 ~]# docker run -itd --name newweb myweb:latest //启动一个容器
[root@Docker2 ~]# docker exec -it newweb /bin/bash //进入容器
[root@4e419b580248 /]# nginx
[root@4e419b580248 /]# nginx //确定已启动nginx服务
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] still could not bind()
[root@4e419b580248 /]# curl 127.0.0.1
TEST WEB

注:这里我们可以看见在docker1主机容器中搭建的简单nginx环境并制作成镜像成功的迁移到了docker2主机上了

以上就是本文的全部内容,希望对大家的学习有所帮助,也希望大家多多支持。

上一篇:linux下快速列出局域网中所有主机名(计算机名)的脚本
下一篇:如何在Ubuntu 18.04(实体机)上配置OpenWRT的开发环境
一句话新闻
一文看懂荣耀MagicBook Pro 16
荣耀猎人回归!七大亮点看懂不只是轻薄本,更是游戏本的MagicBook Pro 16.
人们对于笔记本电脑有一个固有印象:要么轻薄但性能一般,要么性能强劲但笨重臃肿。然而,今年荣耀新推出的MagicBook Pro 16刷新了人们的认知——发布会上,荣耀宣布猎人游戏本正式回归,称其继承了荣耀 HUNTER 基因,并自信地为其打出“轻薄本,更是游戏本”的口号。
众所周知,寻求轻薄本的用户普遍更看重便携性、外观造型、静谧性和打字办公等用机体验,而寻求游戏本的用户则普遍更看重硬件配置、性能释放等硬核指标。把两个看似难以相干的产品融合到一起,我们不禁对它产生了强烈的好奇:作为代表荣耀猎人游戏本的跨界新物种,它究竟做了哪些平衡以兼顾不同人群的各类需求呢?