如果您对(OK)InstallDockeronFedora23感兴趣，那么本文将是一篇不错的选择，我们将为您详在本文中，您将会了解到关于(OK)InstallDockeronFedora23的详细内容
如果您对(OK) Install Docker on Fedora 23感兴趣，那么本文将是一篇不错的选择，我们将为您详在本文中，您将会了解到关于(OK) Install Docker on Fedora 23的详细内容，并且为您提供关于(OK) CentOS7/Fedora23——Installing Docker——core—pip、(OK) Fedora 23——CORE——docker——(1)——> install-kernel、(OK) Fedora 23——CORE——docker——(2)——> install-quagga、(OK) Fedora 23——CORE——docker——(3)——> install-docker的有价值信息。
本文目录一览：- (OK) Install Docker on Fedora 23
- (OK) CentOS7/Fedora23——Installing Docker——core—pip
- (OK) Fedora 23——CORE——docker——(1)——> install-kernel
- (OK) Fedora 23——CORE——docker——(2)——> install-quagga
- (OK) Fedora 23——CORE——docker——(3)——> install-docker
(OK) Install Docker on Fedora 23
---------Install Docker on Fedora 23dnf update -y
dnf -y install docker-io
systemctl start docker
systemctl start docker.service
systemctl restart docker.service
systemctl stop docker.service
systemctl status docker.service
systemctl status docker -l
^^^^^^ 宿主机测试
docker images
docker search centos
docker pull centos
docker images
docker tag 2933d50b9f77 docker.io/centos:core
docker run centos echo "hello world!"
^^^^^^ 至此，宿主机 OK
docker run --rm -it centos /bin/bash
docker run --rm -it -d centos /bin/bash
docker run --rm centos echo "hello world!"
docker run centos echo "hello world!"
docker run --cap-add=NET_ADMIN --cap-add=SYS_ADMIN centos echo "hello world!"
docker run --privileged -ti -v /sys/fs/cgroup:/sys/fs/cgroup centos echo "hello world!"
docker run --privileged -ti -e "container=docker" -v /sys/fs/cgroup:/sys/fs/cgroup centos /usr/sbin/init
(OK) CentOS7/Fedora23——Installing Docker——core—pip
# rpm -ivh ftp://ftp.muug.mb.ca/mirror/centos/7.2.1511/os/x86_64/Packages/PyYAML-3.10-11.el7.x86_64.rpm# yum -y install docker docker-registry OR # yum -y install docker-engine docker-registry
# rpm -qa | grep docker
docker-engine-selinux-1.9.1-1.el7.centos.noarch
docker-registry-0.9.1-7.el7.x86_64
docker-engine-1.9.1-1.el7.centos.x86_64
# rm /etc/docker/key.json
# systemctl daemon-reload
# systemctl start docker.service
# systemctl enable docker.service
# systemctl disable docker.service
# docker version
# docker search centos
# docker pull centos
# docker run -i -t centos /bin/bash
--------------------------------
problem:
[root@localhost ~]# systemctl restart docker
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
[root@localhost ~]# docker daemon
WARN[0000] Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section.
FATA[0000] Error starting daemon: error initializing graphdriver: "/var/lib/docker" contains other graphdrivers: overlay; Please cleanup or explicitly choose storage driver (-s <DRIVER>)
resolve:
# rm /var/lib/docker/overlay/ -rf
--------------------------------
----------------------------------------------
uninstall docker:
----------------------------------------------
systemctl stop docker
systemctl disable docker
systemctl daemon-reload
yum -y remove docker*
rm -rf /etc/docker /var/lib/docker /var/run/docker
----------------------------------------------
core—pip —— refer to /opt/tools/network_simulators/core/core/daemon/core/service.py
----------------------------------------------
curl "https://bootstrap.pypa.io/get-pip.py" -o "get-pip.py"
python get-pip.py
pip --help
pip -V
++++++++++++++++++++++++++++++++++++++++++++
# docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
docker.io/centos latest 60e65a8e4030 4 weeks ago 196.6 MB
# docker tag c8a648134623 docker.io/centos:core
# ls /var/lib/docker/
containers devicemapper graph linkgraph.db network repositories-devicemapper tmp trust volumes
# cat /var/lib/docker/repositories-devicemapper
{"Repositories":{"docker.io/centos":{"latest":"60e65a8e4030022260a4f84166814b2683e1cdfc9725a9c262e90ba9c5ae2332"},"hello-world":{"latest":"0a6ba66e537a53a5ea94f7c6a99c534c6adb12e3ed09326d4bf3b38f7c3ba4e7"}},"ConfirmDefPush":true}
++++++++++++++++++++++++++++++++++++++++++++
Where are docker images stored on the host machine?
++++++++++++++++++++++++++++++++++++++++++++
# docker info
Data file: /var/lib/docker/devicemapper/devicemapper/data
Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata
---------------------------------------------------------------
http://stackoverflow.com/questions/19234831/where-are-docker-images-stored-on-the-host-machine
---------------------------------------------------------------
The contents of the /var/lib/docker directory vary depending on the driver Docker is using for storage.
By default this will be aufs but can fall back to btrfs, devicemapper or vfs. In most places this will be aufs but the RedHats went with devicemapper.
You can manually set the storage driver with the -s or --storage-driver= option to the Docker daemon.
- /var/lib/docker/{driver-name} will contain the driver specific storage for contents of the images.
- /var/lib/docker/graph/ now only contains metadata about the image, in the json and layersize files.
In the case of aufs:
- /var/lib/docker/aufs/diff/ has the file contents of the images.
- /var/lib/docker/repositories-aufs is a JSON file containing local image information. This can be viewed with the command docker images.
In the case of devicemapper:
- /var/lib/docker/devicemapper/devicemapper/data stores the images
- /var/lib/docker/devicemapper/devicemapper/metadata the metadata
- Note these files are thin provisioned "sparse" files so aren''t as big as they seem.
--------------------------------
problem:
[root@localhost ~]# systemctl restart docker
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
[root@localhost ~]# docker daemon
WARN[0000] Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section.
FATA[0000] Error starting daemon: error initializing graphdriver: "/var/lib/docker" contains other graphdrivers: overlay; Please cleanup or explicitly choose storage driver (-s <DRIVER>)
resolve:
# rm /var/lib/docker/overlay/ -rf
--------------------------------
Docker not starting “ could not delete the default bridge network: network bridge has active endpoints”"
Run
sudo mv /var/lib/docker/network/files/ /tmp/dn-bak
to reset your networks. Then restart docker (sudo systemctl restart docker or sudo service docker restart depending on your OS). If everything works again you can delete the dn-bak directory.
--------------------------------
[root@localhost ~]# gedit /etc/sysconfig/docker
DOCKER_OPTS="--dns 8.8.8.8 --dns 75.75.75.76"
DOCKER_OPTS="--iptables=true --dns=10.20.100.1 --dns=8.8.8.8"
--------------------------------
On arch linux I needed
ip link set down docker0 instead of ifconfig docker0 down and
systemctl restart docker instead of service docker start.
To delete all images, I did
docker rmi $(docker images -q)
++++++++++++++++
docker tag c8a648134623 docker.io/centos:core
/etc/sysconfig/docker-storage 这个配置文件
DOCKER_STORAGE_OPTIONS="--storage-opt dm.no_warn_on_loop_devices=true"
or
DOCKER_STORAGE_OPTIONS="-s overlay"
------------------------------------------------------------------------------------------------------
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues
------------------------------------------------------------------------------------------------------
Description of problem:
`docker version`:
`docker info`:
`uname -a`:
Environment details (AWS, VirtualBox, physical, etc.):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual Results:
Expected Results:
Additional info:
------------------------------------------------------------------------------------------------------
(OK) Fedora 23——CORE——docker——(1)——> install-kernel
Information for package kernel
http://koji.fedoraproject.org/koji/packageinfo?packageID=8
dnf install kernel-4.3.3-301.fc23
dnf install kernel-devel-4.3.3-301.fc23
dnf install kernel-headers-4.3.3-301.fc23
dnf install kernel-debug-devel-4.3.3-301.fc23
kernel x86_64 4.3.3-301.fc23 fedora 46 k
kernel-core x86_64 4.3.3-301.fc23 fedora 20 M
kernel-modules x86_64 4.3.3-301.fc23 fedora 18 M
kernel-modules-extra x86_64 4.3.3-301.fc23 fedora
kernel-devel x86_64 4.3.3-301.fc23 fedora 9.8 M
kernel-headers x86_64 4.3.3-301.fc23 fedora 987 k
kernel-debug-devel x86_64 4.3.3-301.fc23 fedora 9.9 M
-----------------------------------------------------------------------------
Information for build kernel-4.4.3-300.fc23
http://koji.fedoraproject.org/koji/buildinfo?buildID=739250
wget https://kojipkgs.fedoraproject.org//packages/kernel/4.4.3/300.fc23/x86_64/kernel-debug-devel-4.4.3-300.fc23.x86_64.rpm
wget https://kojipkgs.fedoraproject.org//packages/kernel/4.4.3/300.fc23/x86_64/kernel-devel-4.4.3-300.fc23.x86_64.rpm
wget https://kojipkgs.fedoraproject.org//packages/kernel/4.4.3/300.fc23/x86_64/kernel-core-4.4.3-300.fc23.x86_64.rpm
wget https://kojipkgs.fedoraproject.org//packages/kernel/4.4.3/300.fc23/x86_64/kernel-modules-4.4.3-300.fc23.x86_64.rpm
wget https://kojipkgs.fedoraproject.org//packages/kernel/4.4.3/300.fc23/x86_64/kernel-modules-extra-4.4.3-300.fc23.x86_64.rpm
wget https://kojipkgs.fedoraproject.org//packages/kernel/4.4.3/300.fc23/x86_64/kernel-4.4.3-300.fc23.x86_64.rpm
wget https://kojipkgs.fedoraproject.org//packages/kernel/4.4.3/300.fc23/x86_64/kernel-headers-4.4.3-300.fc23.x86_64.rpm
下面按顺序 执行
rpm -ivh kernel-debug-devel-4.4.3-300.fc23.x86_64.rpm
rpm -ivh kernel-devel-4.4.3-300.fc23.x86_64.rpm
rpm -ivh kernel-core-4.4.3-300.fc23.x86_64.rpm
rpm -ivh kernel-modules-4.4.3-300.fc23.x86_64.rpm
rpm -ivh kernel-modules-extra-4.4.3-300.fc23.x86_64.rpm
rpm -ivh kernel-4.4.3-300.fc23.x86_64.rpm
暂时没有执行
rpm -ivh kernel-headers-4.4.3-300.fc23.x86_64.rpm
[root @localhost kernel-rpm]# rpm -ivh kernel-headers-4.4.3-300.fc23.x86_64.rpm
错误：依赖检测失败：
kernel-headers < 4.4.8-300.fc23 被 (已安裝) kernel-headers-4.4.8-300.fc23.x86_64 取代
-----------------------------------------------------------------------------
Information for build kernel-4.3.3-301.fc23
http://koji.fedoraproject.org/koji/buildinfo?buildID=711494
wget https://kojipkgs.fedoraproject.org//packages/kernel/4.3.3/301.fc23/x86_64/kernel-debug-devel-4.3.3-301.fc23.x86_64.rpm
wget https://kojipkgs.fedoraproject.org//packages/kernel/4.3.3/301.fc23/x86_64/kernel-devel-4.3.3-301.fc23.x86_64.rpm
wget https://kojipkgs.fedoraproject.org//packages/kernel/4.3.3/301.fc23/x86_64/kernel-core-4.3.3-301.fc23.x86_64.rpm
wget https://kojipkgs.fedoraproject.org//packages/kernel/4.3.3/301.fc23/x86_64/kernel-modules-4.3.3-301.fc23.x86_64.rpm
wget https://kojipkgs.fedoraproject.org//packages/kernel/4.3.3/301.fc23/x86_64/kernel-modules-extra-4.3.3-301.fc23.x86_64.rpm
wget https://kojipkgs.fedoraproject.org//packages/kernel/4.3.3/301.fc23/x86_64/kernel-4.3.3-301.fc23.x86_64.rpm
wget https://kojipkgs.fedoraproject.org//packages/kernel/4.3.3/301.fc23/x86_64/kernel-headers-4.3.3-301.fc23.x86_64.rpm
下面按顺序 执行
rpm -ivh kernel-debug-devel-4.3.3-301.fc23.x86_64.rpm
rpm -ivh kernel-devel-4.3.3-301.fc23.x86_64.rpm
rpm -ivh kernel-core-4.3.3-301.fc23.x86_64.rpm
rpm -ivh kernel-modules-4.3.3-301.fc23.x86_64.rpm
rpm -ivh kernel-modules-extra-4.3.3-301.fc23.x86_64.rpm
rpm -ivh kernel-4.3.3-301.fc23.x86_64.rpm
暂时没有执行
rpm -ivh kernel-headers-4.3.3-301.fc23.x86_64.rpm
[root @localhost kernel-rpm]# rpm -ivh kernel-headers-4.3.3-301.fc23.x86_64.rpm
错误：依赖检测失败：
kernel-headers < 4.4.8-300.fc23 被 (已安裝) kernel-headers-4.4.8-300.fc23.x86_64 取代
-----------------------------------------------------------------------------
rpm --oldpackage -ivh kernel-debug-devel-4.3.3-301.fc23.x86_64.rpm
rpm --oldpackage -ivh kernel-devel-4.3.3-301.fc23.x86_64.rpm
rpm --oldpackage -ivh kernel-core-4.3.3-301.fc23.x86_64.rpm
rpm --oldpackage -ivh kernel-modules-4.3.3-301.fc23.x86_64.rpm
rpm --oldpackage -ivh kernel-modules-extra-4.3.3-301.fc23.x86_64.rpm
rpm --oldpackage -ivh kernel-4.3.3-301.fc23.x86_64.rpm
下面由于版本问题，暂时不执行
rpm --oldpackage -ivh kernel-headers-4.3.3-301.fc23.x86_64.rpm
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
dnf - Fedora23——删除多余不用的内核
http://blog.csdn.net/ztguang/article/details/51302063
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[root @localhost ~]# uname -r
uname -r
4.3.5-300.fc23.x86_64
[root @localhost ~]# rpm -qa | grep kernel |grep 4.4.8
rpm -qa | grep kernel |grep 4.4.8
kernel-core-4.4.8-300.fc23.x86_64
kernel-headers-4.4.8-300.fc23.x86_64
kernel-modules-4.4.8-300.fc23.x86_64
kernel-modules-extra-4.4.8-300.fc23.x86_64
kernel-devel-4.4.8-300.fc23.x86_64
kernel-4.4.8-300.fc23.x86_64
[root @localhost ~]#
dnf remove kernel-core-4.4.8-300.fc23.x86_64
dnf remove kernel-devel-4.4.8-300.fc23.x86_64
dnf remove kernel-modules-4.4.8-300.fc23.x86_64
dnf remove kernel-modules-extra-4.4.8-300.fc23.x86_64
dnf remove kernel-4.4.8-300.fc23.x86_64
下面这条命令暂时不执行，因为要删除的包太多
dnf remove kernel-headers-4.4.8-300.fc23.x86_64
[root@localhost ~]# dnf remove kernel-headers-4.4.8-300.fc23.x86_64
===================================================================
移除 226 软件包
安装大小：754 M
确定吗？[y/N]： n
操作中止。
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
删除内核：4.3.5
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[root@localhost ~]# rpm -qa | grep kernel |grep 4.3.5
kernel-modules-4.3.5-300.fc23.x86_64
kernel-4.3.5-300.fc23.x86_64
kernel-devel-4.3.5-300.fc23.x86_64
kernel-core-4.3.5-300.fc23.x86_64
kernel-modules-extra-4.3.5-300.fc23.x86_64
kernel-debug-devel-4.3.5-300.fc23.x86_64
[root@localhost ~]#
dnf remove kernel-modules-4.3.5-300.fc23.x86_64
dnf remove kernel-4.3.5-300.fc23.x86_64
dnf remove kernel-devel-4.3.5-300.fc23.x86_64
dnf remove kernel-core-4.3.5-300.fc23.x86_64
dnf remove kernel-modules-extra-4.3.5-300.fc23.x86_64
dnf remove kernel-debug-devel-4.3.5-300.fc23.x86_64
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
(OK) Fedora 23——CORE——docker——(2)——> install-quagga
-------------------Installing Quagga on Fedora 23
# dnf group install ''Development Tools'' [on Fedora 22+ Versions]
/opt/tools/network_simulators/quagga/quagga-svnsnap.tgz
-rwxrwx---. 1 root root 2471193 1 月 13 21:57 quagga-0.99.21mr2.2.tar.gz
-rwxrwx---. 1 root root 2560375 1 月 14 14:27 quagga-svnsnap.tgz
# tar xzf quagga-svnsnap.tgz
# cd quagga
[root @localhost quagga]# ./bootstrap.sh
[root @localhost quagga]# ./configure --enable-user=root --enable-group=root --with-cflags=-ggdb --sysconfdir=/usr/local/etc/quagga --enable-vtysh --localstatedir=/var/run/quagga
// copy basic.texi, ipv6.texi in quagga-0.99.24/doc to quagga-0.99.21mr2.2/doc
[root @localhost quagga]# cp ../quagga-0.99.24/doc/basic.texi ../quagga-0.99.24/doc/ipv6.texi doc/
[root @localhost quagga]# make -j4
[root @localhost quagga]# make install
---------------------------------------------------------------------------------
[root@localhost quagga]# pwd
/root/core-tools/quagga
/bin/cp pimd/pimd.conf.sample /usr/local/etc/quagga/pimd.conf
/bin/cp isisd/isisd.conf.sample /usr/local/etc/quagga/isisd.conf
/bin/cp babeld/babeld.conf.sample /usr/local/etc/quagga/babeld.conf
/bin/cp ospf6d/ospf6d.conf.sample /usr/local/etc/quagga/ospf6d.conf
/bin/cp ospfd/ospfd.conf.sample /usr/local/etc/quagga/ospfd.conf
/bin/cp ripngd/ripngd.conf.sample /usr/local/etc/quagga/ripngd.conf
/bin/cp ripd/ripd.conf.sample /usr/local/etc/quagga/ripd.conf
/bin/cp bgpd/bgpd.conf.sample /usr/local/etc/quagga/bgpd.conf
/bin/cp zebra/zebra.conf.sample /usr/local/etc/quagga/zebra.conf
/bin/cp vtysh/vtysh.conf.sample /usr/local/etc/quagga/vtysh.conf
ln -s /usr/local/etc/quagga/pimd.conf /etc/quagga/pimd.conf
ln -s /usr/local/etc/quagga/isisd.conf /etc/quagga/isisd.conf
ln -s /usr/local/etc/quagga/babeld.conf /etc/quagga/babeld.conf
ln -s /usr/local/etc/quagga/ospf6d.conf /etc/quagga/ospf6d.conf
ln -s /usr/local/etc/quagga/ospfd.conf /etc/quagga/ospfd.conf
ln -s /usr/local/etc/quagga/ripngd.conf /etc/quagga/ripngd.conf
ln -s /usr/local/etc/quagga/ripd.conf /etc/quagga/ripd.conf
ln -s /usr/local/etc/quagga/bgpd.conf /etc/quagga/bgpd.conf
ln -s /usr/local/etc/quagga/zebra.conf /etc/quagga/zebra.conf
ln -s /usr/local/etc/quagga/vtysh.conf /etc/quagga/vtysh.conf
/bin/cp /usr/local/etc/quagga/zebra.conf /usr/local/etc/quagga/Quagga.conf
---------------------------------------------------------------------------------
// # cp /etc/sysconfig/quagga.bac /etc/sysconfig/quagga //this command is not used
# gedit /usr/lib/systemd/system/zebra.service
[Unit]
Description=GNU Zebra routing manager
Wants=network.target
Before=network.target
ConditionPathExists=/usr/local/etc/quagga/zebra.conf
[Service]
Type=forking
PIDFile=/run/quagga/zebra.pid
EnvironmentFile=-/etc/sysconfig/quagga
ExecStartPre=/sbin/ip route flush proto zebra
ExecStart=/usr/local/sbin/zebra -d $ZEBRA_OPTS -f /usr/local/etc/quagga/zebra.conf
Restart=on-abort
[Install]
WantedBy=multi-user.target
---------------------------------------------------------------------------------
[root@localhost quagga]# systemctl cat zebra.service
[root@localhost quagga]# systemctl start zebra.service
Job for zebra.service failed because a configured resource limit was exceeded. See "systemctl status zebra.service" and "journalctl -xe" for details.
[root@localhost quagga]# mkdir /run/quagga/
[root@localhost quagga]# systemctl start zebra.service
[root@localhost quagga]# systemctl status zebra.service
[root@localhost quagga]# systemctl stop zebra.service
[root@localhost quagga]# vtysh
[root@localhost quagga]# telnet localhost 2601
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
So far, OK
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
configure.ac:217: error: possibly undefined macro: AC_PROG_LIBTOOL
[root@localhost quagga]# dnf install libtool
[root@localhost quagga]# dnf install autoconf-archive
//automake: You are advised to start using ''subdir-objects'' option throughout your
[root@localhost quagga]# gedit configure.ac
dnl AM_INIT_AUTOMAKE(1.6)
AM_INIT_AUTOMAKE([subdir-objects])
[root@localhost quagga]# ./bootstrap.sh
[root@localhost quagga]# dnf install gcc-c++
[root@localhost quagga]# ./configure --enable-user=root --enable-group=root --with-cflags=-ggdb --sysconfdir=/usr/local/etc/quagga --enable-vtysh --localstatedir=/var/run/quagga
// 下面一行暂不需要
// copy basic.texi, ipv6.texi in quagga-0.99.24/doc to quagga-0.99.21mr2.2/doc
// makeinfo: command not found
[root@localhost quagga]# dnf install texinfo
# make -j4
# make install
[root@localhost quagga]# pwd
cp pimd/pimd.conf.sample /usr/local/etc/quagga/pimd.conf
cp isisd/isisd.conf.sample /usr/local/etc/quagga/isisd.conf
cp babeld/babeld.conf.sample /usr/local/etc/quagga/babeld.conf
cp ospf6d/ospf6d.conf.sample /usr/local/etc/quagga/ospf6d.conf
cp ospfd/ospfd.conf.sample /usr/local/etc/quagga/ospfd.conf
cp ripngd/ripngd.conf.sample /usr/local/etc/quagga/ripngd.conf
cp ripd/ripd.conf.sample /usr/local/etc/quagga/ripd.conf
cp bgpd/bgpd.conf.sample /usr/local/etc/quagga/bgpd.conf
cp zebra/zebra.conf.sample /usr/local/etc/quagga/zebra.conf
cp vtysh/vtysh.conf.sample /usr/local/etc/quagga/vtysh.conf
ln -s /usr/local/etc/quagga/pimd.conf /etc/quagga/pimd.conf
ln -s /usr/local/etc/quagga/isisd.conf /etc/quagga/isisd.conf
ln -s /usr/local/etc/quagga/babeld.conf /etc/quagga/babeld.conf
ln -s /usr/local/etc/quagga/ospf6d.conf /etc/quagga/ospf6d.conf
ln -s /usr/local/etc/quagga/ospfd.conf /etc/quagga/ospfd.conf
ln -s /usr/local/etc/quagga/ripngd.conf /etc/quagga/ripngd.conf
ln -s /usr/local/etc/quagga/ripd.conf /etc/quagga/ripd.conf
ln -s /usr/local/etc/quagga/bgpd.conf /etc/quagga/bgpd.conf
ln -s /usr/local/etc/quagga/zebra.conf /etc/quagga/zebra.conf
ln -s /usr/local/etc/quagga/vtysh.conf /etc/quagga/vtysh.conf
cp /usr/local/etc/quagga/zebra.conf /usr/local/etc/quagga/Quagga.conf
-------------------Fedora 23, Installing Quagga
------/root/core-tools/quagga/missing: 行 81: makeinfo: 未找到命令
------need to: dnf install texinfo
# tar xzf quagga-svnsnap.tgz
# cd quagga
[root@localhost quagga]# ./bootstrap.sh
[root@localhost quagga]# ./configure --enable-user=root --enable-group=root --with-cflags=-ggdb --sysconfdir=/usr/local/etc/quagga --enable-vtysh --localstatedir=/var/run/quagga
// copy basic.texi, ipv6.texi in quagga-0.99.24/doc to quagga-0.99.21mr2.2/doc
[root@localhost quagga]# cp ../quagga-0.99.24/doc/basic.texi ../quagga-0.99.24/doc/ipv6.texi doc/
[root@localhost quagga]# make -j4
[root@localhost quagga]# make install
[root@localhost quagga]# systemctl cat zebra.service
[root@localhost quagga]# systemctl start zebra.service
Job for zebra.service failed because a configured resource limit was exceeded. See "systemctl status zebra.service" and "journalctl -xe" for details.
[root@localhost quagga]# mkdir /run/quagga/
[root@localhost quagga]# systemctl start zebra.service
[root@localhost quagga]# systemctl status zebra.service
[root@localhost quagga]# systemctl stop zebra.service
[root@localhost quagga]# vtysh
[root@localhost quagga]# telnet localhost 2601
+++++++++++++++++++++++++++++
(OK) Fedora 23——CORE——docker——(3)——> install-docker
+++++++++++++++++++++++++ install docker etc.# Fedora 23
dnf install openvswitch docker-io xterm wireshark-gnome ImageMagick tcl tcllib tk kernel-modules-extra util-linux
----------------------------------------------------
install docker 1.9.1
----------------------------------------------------
//docker 1.9.1
//dnf update --exclude=kernel*
//dnf update
dnf remove docker
dnf install docker-io
rm /var/lib/docker/ -rf
ls /var/lib/docker/
systemctl start docker
systemctl stop docker
systemctl status docker
systemctl enable docker
docker search busybox
docker pull busybox
docker images
docker tag 307ac631f1b5 docker.io/busybox:core
docker rmi docker.io/busybox:core
docker run --rm -it busybox /bin/sh
dnf remove docker-io
rm /var/lib/docker/ -rf
----------------------------------------------------
So far, OK
----------------------------------------------------
https://docs.docker.com/engine/installation/linux/fedora/
install docker 1.11.1
----------------------------------------------------
tee /etc/yum.repos.d/docker.repo <<-''EOF''
[dockerrepo]
name=Docker Repository
baseurl=https://yum.dockerproject.org/repo/main/fedora/$releasever/
enabled=1
gpgcheck=1
gpgkey=https://yum.dockerproject.org/gpg
EOF
----------------------------------------------------
//docker 1.11.1
//dnf update
dnf update --exclude=kernel*
init 6
dnf update
dnf install docker-engine
dnf remove docker-engine
----------------------------------------------------
dnf install docker-engine-1.10.3 docker-engine-selinux-1.10.3
---------------------------------------------------- the two following lines, not use
# echo ''DOCKER_STORAGE_OPTIONS="-s overlay"'' >> /etc/sysconfig/docker-storage
# systemctl restart docker
----------------------------------------------------
ls /etc/systemd/system
ls /usr/lib/systemd/system
ls /usr/lib/systemd/system/docker.service
rm /var/lib/docker/overlay/ -rf
rm /var/lib/docker/ -rf
----------------------------------------------------
[root @localhost 桌面]# gedit /usr/lib/systemd/system/docker.service
# ExecStart=/usr/bin/docker daemon -H fd://
ExecStart=/usr/bin/docker daemon -s overlay
systemctl start docker.service
systemctl restart docker.service
systemctl stop docker.service
systemctl status docker.service
systemctl daemon-reload
----------------------------------------------------
Work around for me right now is to downgrade to 1.6.2.
# yum downgrade docker-1.6.2-14.el7.centos
# systemctl restart docker
----------------------------------------------------
docker info
docker version
----------------------------------------------------
[root @localhost 桌面]#
docker search busybox
docker pull busybox
docker images
docker tag 47bcc53f74dc busybox:core
docker rmi busybox:core
docker run --rm -it busybox /bin/sh
[root @localhost 桌面]# docker logs $(docker ps -q) | tail -20
[root @n2 n2.conf]#
docker daemon -s overlay &
docker run --rm -it busybox /bin/sh
rm /var/lib/docker/ -rf
----------------------------------------------------
So far, OK
----------------------------------------------------
docker run hello-world
systemctl status systemd-udevd.service -l
//List Containers
docker ps
docker ps -a
docker ps -l
//Attach to a Specific Container
docker attach 9c09acd48a25
//View Logs for a Docker Container 2c9d5e12800e
docker logs 2c9d5e12800e
docker images
docker tag 778a53015523 centos:core
docker search centos
docker pull centos
docker images
docker rmi 778a53015523
docker tag 40467a0b3d66 centos:core
docker tag 44776f55294a ubuntu:core
docker run hello-world
docker run centos echo "hello world!"
docker run ubuntu echo "hello world!"
docker run ubuntu:core echo "hello world!"
docker run -it busybox /bin/sh
docker run --rm -it busybox /bin/sh
docker tag 307ac631f1b5 docker.io/busybox:core
docker run --rm -it busybox:core /bin/sh
docker run -v /tmp/dockerdev:/dev -it --rm centos:core bash
docker run -d --net host --name coreDock busybox /bin/sh
docker ps -a
brctl show
ldd $(which docker)
ps aux |grep docker
----------------------------------------------------
----------
如果出现如下问题：
# systemctl start docker
Job for docker.service failed. See ''systemctl status docker.service'' and ''journalctl -xn'' for details.
解决方法：
# rm /var/lib/docker -rf
# systemctl daemon-reload
# systemctl start docker
--------------------------------------------------------------------------------------------------------------
http://stackoverflow.com/questions/20994863/how-to-use-docker-or-linux-containers-for-network-emulation
--------------------------------------------------------------------------------------------------------------
CORE Network Emulator does have a Docker Service that I contributed and wrote an article about. The initial version that is in 4.8 is mostly broken but I have fixed and improved it. A pull request is on GitHub.
The service allows you to tag Docker Images with ''core'' and then they appear as an option in the services settings. You must select the Docker image which starts the docker service in the container. You then select the container or containers that you want to run in that node. It scales quite well and I have had over 2000 nodes on my 16Gb machine.
You mentioned OVS as well. This is not yet built in to CORE but can be used manually. I just answered a question on the CORE mailing list on this. It gives a brief overview of switching out a standard CORE switch(bridge) with OVS. Text reproduced below if it is useful:
--------------------------------------------------------------------------------------------------------------
我们今天的关于(OK) Install Docker on Fedora 23的分享就到这里，谢谢您的阅读，如果想了解更多关于(OK) CentOS7/Fedora23——Installing Docker——core—pip、(OK) Fedora 23——CORE——docker——(1)——> install-kernel、(OK) Fedora 23——CORE——docker——(2)——> install-quagga、(OK) Fedora 23——CORE——docker——(3)——> install-docker的相关信息，可以在本站进行搜索。
本文标签：
