dockerLinux环境下安装
使用docker安装itop
使⽤docker安装itop使⽤docker安装itop链接：1，系统：centos7，#关闭防⽕墙，selinux安装docker服务，启动#systemctl status docker#systemctl start docker#docker image ls 查看docker镜像#docker container ls 查看docker容器#docker ps 查看docker容器#docker ps -a查看所有容器记录（包括未运⾏的容器），并查看那些容器是使⽤了这个要删除的镜像：#docker rm 容器ID 删除容器#docker rmi 镜像ID 删除镜像2，启动itop的docker#docker run -d -p 80:80 --name=my-itop -v /itop/itop-extensions:/var/www/html/extensions vbkunin/itop:2.7.0-beta#docker ps#docker start my-itop 启动 my-itop的docker#docker exec -it f6a41ffe526c(容器ID) /bin/bash 进⼊容器的交互环境登录ITOP web页⾯，http://itop-IP/3，copy⽂件进docker# docker cp iTopDataModelToolkit-2.3.zip cc5021e676b1:/var/www/html/#docker ps#docker exec -it cc5021e676b1 /bin/bash 进⼊docker#cd /var/www/html/#unzip iTopDataModelToolkit-2.3.zip登录toolkit链接：http://ITOP-IP/toolkit4, 从容器中copy出⽂件从docker中 copy出⽂件Docker cp命令: ⽤于容器与主机之间的数据copy语法: docker cp [OPTIONS] container:src_path dest_path docker cp [OPTIONS]#docker cp 容器ID:/usr/xxx.txt /usr/xxx.txt5，定制化定制字段定制类6，常见错误（1）加载初始化⾃定义模块，会报错，找到config-itop.php后，赋予775权限，即可。
CentOS7安装docker解决启动不了的问题
CentOS7安装docker解决启动不了的问题CentOS7安装docker 启动不了，在⼯作当中遇到这个问题，当时急的不清，⽹上资料⼜不多，不过经过⾃⼰的捣⿎终于解决了这个问题！[root@test ~]# yum update[root@test ~]# yum install docker[root@test ~]# service docker startRedirecting to /bin/systemctl start docker.serviceJob for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.[root@test ~]# systemctl status docker.service● docker.service - Docker Application Container EngineLoaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)Active: inactive (dead) (Result: exit-code) since 四 2016-03-10 13:01:21 CST; 7s agoDocs: Process: 29939 ExecStart=/usr/bin/docker daemon $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $ADD_REGISTRY $BLOCK_REGISTRY $INSECURE_REGISTRY (code=exited, status=2) Main PID: 29939 (code=exited, status=2)CGroup: /system.slice/docker.service└─29970 mkfs.ext4 -E nodiscard,lazy_itable_init=0,lazy_journal_ini...3⽉ 10 13:01:20 systemd[1]: Failed to start Docker Applic....3⽉ 10 13:01:20 systemd[1]: Unit docker.service entered f....3⽉ 10 13:01:20 systemd[1]: docker.service failed.3⽉ 10 13:01:21 systemd[1]: docker.service holdoff time o....Hint: Some lines were ellipsized, use -l to show in full.[root@test ~]#使⽤yum install docker安装完后启动不了[root@apptest ~]# service docker startRedirecting to /bin/systemctl start docker.service⼀直停留在以上步骤可以使⽤以下命令来安装，即可成功。
CentOS7安装Docker时的异常报错与解决方法
CentOS7安装Docker时的异常报错与解决⽅法重要：有些⼈在vmware中安装了新的centos⽤于使⽤docker，但是往往会忽略了更换源与进⾏系统update，这样会导致安装过程中出现诸多如下类问题，为了避免不必要的⿇烦在安装docker前最好最到⼀下⼏点：1.替换centos源为163或其他更适合的源,具体操作可以查看我另⼀篇⽂章《》2.清空缓存（yum clean\ yum makecache）3.系统更新（yum update）确认环境[root@localhost ~]# cat /etc/redhat-releaseCentOS Linux release 7.0.1406 (Core)docker安装－> 报错[root@localhost ~]# yum install dockerLoaded plugins: fastestmirror, langpacksRepodata is over 2 weeks old. Install yum-cron? Or run: yum makecache fastExisting lock /var/run/yum.pid: another copy is running as pid 11946.Another app is currently holding the yum lock; waiting for it to exit...The other application is: PackageKitMemory : 39 M RSS (444 MB VSZ)Started: Thu Jul 722:42:132016 - 08:57 agoState : Sleeping, pid: 11946解决⽅法rm -rf /run/yum.pid[root@localhost run]# rm -rf /run/yum.pid继续docker安装－> 报错[root@localhost run]# yum install dockerLoaded plugins: fastestmirror, langpacksRepodata is over 2 weeks old. Install yum-cron? Or run: yum makecache fastbase | 3.6 kB 00:00:00extras | 3.4 kB 00:00:00updates | 3.4 kB 00:00:00(1/2): extras/7/x86_64/primary_db | 149 kB 00:00:00(2/2): updates/7/x86_64/primary_db | 5.7 MB 00:00:47Determining fastest mirrors* base: * extras: * updates: Resolving Dependencies--> Running transaction check---> Package docker.x86_64 0:1.10.3-44.el7.centos will be installed--> Processing Dependency: oci-systemd-hook = 1.10.3-44.el7.centos for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: oci-register-machine = 1.10.3-44.el7.centos for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: docker-forward-journald = 1.10.3-44.el7.centos for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: docker-common = 1.10.3-44.el7.centos for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: selinux-policy >= 3.13.1-23for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: docker-selinux >= 1.10.3-44.el7.centos for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: device-mapper-libs >= 7:1.02.97for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: libsystemd.so.0(LIBSYSTEMD_209)(64bit) for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_97)(64bit) for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: libsystemd.so.0()(64bit) for package: docker-1.10.3-44.el7.centos.x86_64--> Running transaction check---> Package device-mapper-libs.x86_64 7:1.02.84-14.el7 will be updated--> Processing Dependency: device-mapper-libs = 7:1.02.84-14.el7 for package: 7:device-mapper-1.02.84-14.el7.x86_64---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7_2.5 will be an update---> Package docker-common.x86_64 0:1.10.3-44.el7.centos will be installed---> Package docker-forward-journald.x86_64 0:1.10.3-44.el7.centos will be installed---> Package docker-selinux.x86_64 0:1.10.3-44.el7.centos will be installed--> Processing Dependency: selinux-policy-targeted >= 3.13.1-23for package: docker-selinux-1.10.3-44.el7.centos.x86_64--> Processing Dependency: selinux-policy-base >= 3.13.1-23for package: docker-selinux-1.10.3-44.el7.centos.x86_64---> Package oci-register-machine.x86_64 0:1.10.3-44.el7.centos will be installed---> Package oci-systemd-hook.x86_64 0:1.10.3-44.el7.centos will be installed---> Package selinux-policy.noarch 0:3.12.1-153.el7 will be updated---> Package selinux-policy.noarch 0:3.13.1-60.el7_2.7 will be an update---> Package systemd-libs.x86_64 0:208-11.el7 will be updated--> Processing Dependency: systemd-libs = 208-11.el7 for package: systemd-208-11.el7.x86_64---> Package systemd-libs.x86_64 0:219-19.el7_2.11 will be an update--> Running transaction check---> Package device-mapper.x86_64 7:1.02.84-14.el7 will be updated--> Processing Dependency: device-mapper = 7:1.02.84-14.el7 for package: 7:device-mapper-event-1.02.84-14.el7.x86_64---> Package device-mapper.x86_64 7:1.02.107-5.el7_2.5 will be an update---> Package selinux-policy-targeted.noarch 0:3.12.1-153.el7 will be updated---> Package selinux-policy-targeted.noarch 0:3.13.1-60.el7_2.7 will be an update---> Package systemd.x86_64 0:208-11.el7 will be updated--> Processing Dependency: systemd = 208-11.el7 for package: libgudev1-208-11.el7.x86_64--> Processing Dependency: systemd = 208-11.el7 for package: systemd-sysv-208-11.el7.x86_64--> Processing Dependency: systemd = 208-11.el7 for package: systemd-python-208-11.el7.x86_64---> Package systemd.x86_64 0:219-19.el7_2.11 will be an update--> Processing Dependency: kmod >= 18-4for package: systemd-219-19.el7_2.11.x86_64--> Running transaction check---> Package device-mapper-event.x86_64 7:1.02.84-14.el7 will be updated---> Package device-mapper-event.x86_64 7:1.02.107-5.el7_2.5 will be an update--> Processing Dependency: device-mapper-event-libs = 7:1.02.107-5.el7_2.5for package: 7:device-mapper-event-1.02.107-5.el7_2.5.x86_64---> Package kmod.x86_64 0:14-9.el7 will be updated---> Package kmod.x86_64 0:20-5.el7 will be an update---> Package libgudev1.x86_64 0:208-11.el7 will be updated---> Package libgudev1.x86_64 0:219-19.el7_2.11 will be an update---> Package systemd-python.x86_64 0:208-11.el7 will be updated---> Package systemd-python.x86_64 0:219-19.el7_2.11 will be an update---> Package systemd-sysv.x86_64 0:208-11.el7 will be updated---> Package systemd-sysv.x86_64 0:219-19.el7_2.11 will be an update--> Running transaction check---> Package device-mapper-event-libs.x86_64 7:1.02.84-14.el7 will be updated---> Package device-mapper-event-libs.x86_64 7:1.02.107-5.el7_2.5 will be an update--> Processing Conflict: systemd-219-19.el7_2.11.x86_64 conflicts initscripts < 9.49.28-1--> Restarting Dependency Resolution with new changes.--> Running transaction check---> Package initscripts.x86_64 0:9.49.17-1.el7 will be updated---> Package initscripts.x86_64 0:9.49.30-1.el7_2.2 will be an update--> Processing Conflict: systemd-219-19.el7_2.11.x86_64 conflicts dracut < 033-243--> Restarting Dependency Resolution with new changes.--> Running transaction check---> Package dracut.x86_64 0:033-161.el7 will be updated--> Processing Dependency: dracut = 033-161.el7 for package: dracut-config-rescue-033-161.el7.x86_64--> Processing Dependency: dracut = 033-161.el7 for package: dracut-network-033-161.el7.x86_64---> Package dracut.x86_64 0:033-360.el7_2.1 will be an update--> Running transaction check---> Package dracut-config-rescue.x86_64 0:033-161.el7 will be updated---> Package dracut-config-rescue.x86_64 0:033-360.el7_2.1 will be an update---> Package dracut-network.x86_64 0:033-161.el7 will be updated---> Package dracut-network.x86_64 0:033-360.el7_2.1 will be an update--> Finished Dependency ResolutionDependencies Resolved============================================================================================================================================ Package Arch Version Repository Size============================================================================================================================================ Installing:docker x86_64 1.10.3-44.el7.centos extras 8.6 MUpdating:dracut x86_64 033-360.el7_2.1 updates 311 kinitscripts x86_64 9.49.30-1.el7_2.2 updates 429 kInstalling for dependencies:docker-common x86_64 1.10.3-44.el7.centos extras 59 kdocker-forward-journald x86_64 1.10.3-44.el7.centos extras 831 kdocker-selinux x86_64 1.10.3-44.el7.centos extras 77 koci-register-machine x86_64 1.10.3-44.el7.centos extras 1.0 Moci-systemd-hook x86_64 1.10.3-44.el7.centos extras 96 kUpdating for dependencies:device-mapper x86_64 7:1.02.107-5.el7_2.5 updates 252 kdevice-mapper-event x86_64 7:1.02.107-5.el7_2.5 updates 167 kdevice-mapper-event-libs x86_64 7:1.02.107-5.el7_2.5 updates 169 kdevice-mapper-libs x86_64 7:1.02.107-5.el7_2.5 updates 305 kdracut-config-rescue x86_64 033-360.el7_2.1 updates 50 kdracut-network x86_64 033-360.el7_2.1 updates 90 kkmod x86_64 20-5.el7 base114 klibgudev1 x86_64 219-19.el7_2.11 updates 66 kselinux-policy noarch 3.13.1-60.el7_2.7 updates 376 kselinux-policy-targeted noarch 3.13.1-60.el7_2.7 updates 3.9 Msystemd x86_64 219-19.el7_2.11 updates 5.1 Msystemd-libs x86_64 219-19.el7_2.11 updates 358 ksystemd-python x86_64 219-19.el7_2.11 updates 99 ksystemd-sysv x86_64 219-19.el7_2.11 updates 53 kTransaction Summary============================================================================================================================================ Install 1 Package (+ 5 Dependent packages)Upgrade 2 Packages (+14 Dependent packages)Total download size: 23 MIs this ok [y/d/N]: yDownloading packages:No Presto metadata available for baseupdates/7/x86_64/prestodelta | 603 kB 00:00:00warning: /var/cache/yum/x86_64/7/updates/packages/device-mapper-1.02.107-5.el7_2.5.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEYPublic key for device-mapper-1.02.107-5.el7_2.5.x86_64.rpm is not installed(1/22): device-mapper-1.02.107-5.el7_2.5.x86_64.rpm | 252 kB 00:00:00(2/22): device-mapper-event-libs-1.02.107-5.el7_2.5.x86_64.rpm | 169 kB 00:00:00Public key for docker-forward-journald-1.10.3-44.el7.centos.x86_64.rpm is not installed ] 0.0 B/s | 1.2 MB --:--:-- ETA(3/22): docker-forward-journald-1.10.3-44.el7.centos.x86_64.rpm | 831 kB 00:00:00(4/22): docker-selinux-1.10.3-44.el7.centos.x86_64.rpm | 77 kB 00:00:00(5/22): docker-common-1.10.3-44.el7.centos.x86_64.rpm | 59 kB 00:00:00(6/22): dracut-033-360.el7_2.1.x86_64.rpm | 311 kB 00:00:00(7/22): dracut-network-033-360.el7_2.1.x86_64.rpm | 90 kB 00:00:00(8/22): device-mapper-event-1.02.107-5.el7_2.5.x86_64.rpm | 167 kB 00:00:01(9/22): initscripts-9.49.30-1.el7_2.2.x86_64.rpm | 429 kB 00:00:00Public key for kmod-20-5.el7.x86_64.rpm is not installed(10/22): kmod-20-5.el7.x86_64.rpm | 114 kB 00:00:00(11/22): libgudev1-219-19.el7_2.11.x86_64.rpm | 66 kB 00:00:00(12/22): oci-systemd-hook-1.10.3-44.el7.centos.x86_64.rpm | 96 kB 00:00:00(13/22): device-mapper-libs-1.02.107-5.el7_2.5.x86_64.rpm | 305 kB 00:00:01(14/22): selinux-policy-3.13.1-60.el7_2.7.noarch.rpm | 376 kB 00:00:00(15/22): dracut-config-rescue-033-360.el7_2.1.x86_64.rpm | 50 kB 00:00:00(16/22): systemd-libs-219-19.el7_2.11.x86_64.rpm | 358 kB 00:00:02(17/22): docker-1.10.3-44.el7.centos.x86_64.rpm | 8.6 MB 00:00:03(18/22): systemd-python-219-19.el7_2.11.x86_64.rpm | 99 kB 00:00:00(19/22): systemd-sysv-219-19.el7_2.11.x86_64.rpm | 53 kB 00:00:00(20/22): oci-register-machine-1.10.3-44.el7.centos.x86_64.rpm | 1.0 MB 00:00:03(21/22): selinux-policy-targeted-3.13.1-60.el7_2.7.noarch.rpm | 3.9 MB 00:00:03(22/22): systemd-219-19.el7_2.11.x86_64.rpm | 5.1 MB 00:00:05--------------------------------------------------------------------------------------------------------------------------------------------Total 3.1 MB/s | 23 MB 00:00:07Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7Importing GPG key 0xF4A80EB5:Userid : "CentOS-7 Key (CentOS 7 Official Signing Key) <security@>"Fingerprint: 6341 ab27 53d7 8a78 a7c2 7bb1 24c6 a8a7 f4a8 0eb5Package : centos-release-7-0.1406.el7.centos.2.3.x86_64 (@anaconda)From : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7Is this ok [y/N]: yRunning transaction checkRunning transaction testTransaction check error:file /usr/lib/systemd/system/blk-availability.service from install of device-mapper-7:1.02.107-5.el7_2.5.x86_64 conflicts with file from package lvm2-7:2.02.105-14.el7.x86_64file /usr/sbin/blkdeactivate from install of device-mapper-7:1.02.107-5.el7_2.5.x86_64 conflicts with file from package lvm2-7:2.02.105-14.el7.x86_64file /usr/share/man/man8/blkdeactivate.8.gz from install of device-mapper-7:1.02.107-5.el7_2.5.x86_64 conflicts with file from package lvm2-7:2.02.105-14.el7.x86_64Error Summary-------------解决⽅法yum install libdevmapper* -y[root@localhost run]# yum install libdevmapper* -yLoaded plugins: fastestmirror, langpacksLoading mirror speeds from cached hostfile* base: * extras: * updates: Resolving Dependencies--> Running transaction check---> Package device-mapper-event-libs.x86_64 7:1.02.84-14.el7 will be updated--> Processing Dependency: device-mapper-event-libs = 7:1.02.84-14.el7 for package: 7:device-mapper-event-1.02.84-14.el7.x86_64---> Package device-mapper-event-libs.x86_64 7:1.02.107-5.el7_2.5 will be an update---> Package device-mapper-libs.x86_64 7:1.02.84-14.el7 will be updated--> Processing Dependency: device-mapper-libs = 7:1.02.84-14.el7 for package: 7:device-mapper-1.02.84-14.el7.x86_64---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7_2.5 will be an update---> Package lvm2-libs.x86_64 7:2.02.105-14.el7 will be updated--> Processing Dependency: lvm2-libs = 7:2.02.105-14.el7 for package: 7:lvm2-2.02.105-14.el7.x86_64---> Package lvm2-libs.x86_64 7:2.02.130-5.el7_2.5 will be an update--> Running transaction check---> Package device-mapper.x86_64 7:1.02.84-14.el7 will be updated---> Package device-mapper.x86_64 7:1.02.107-5.el7_2.5 will be an update---> Package device-mapper-event.x86_64 7:1.02.84-14.el7 will be updated---> Package device-mapper-event.x86_64 7:1.02.107-5.el7_2.5 will be an update---> Package lvm2.x86_64 7:2.02.105-14.el7 will be updated---> Package lvm2.x86_64 7:2.02.130-5.el7_2.5 will be an update--> Processing Dependency: device-mapper-persistent-data >= 0.5.5-1for package: 7:lvm2-2.02.130-5.el7_2.5.x86_64--> Running transaction check---> Package device-mapper-persistent-data.x86_64 0:0.3.2-1.el7 will be updated---> Package device-mapper-persistent-data.x86_64 0:0.5.5-1.el7 will be an update--> Finished Dependency ResolutionDependencies Resolved============================================================================================================================================ Package Arch Version Repository Size============================================================================================================================================ Updating:device-mapper-event-libs x86_64 7:1.02.107-5.el7_2.5 updates 169 kdevice-mapper-libs x86_64 7:1.02.107-5.el7_2.5 updates 305 klvm2-libs x86_64 7:2.02.130-5.el7_2.5 updates 873 kUpdating for dependencies:device-mapper x86_64 7:1.02.107-5.el7_2.5 updates 252 kdevice-mapper-event x86_64 7:1.02.107-5.el7_2.5 updates 167 kdevice-mapper-persistent-data x86_64 0.5.5-1.el7 base350 klvm2 x86_64 7:2.02.130-5.el7_2.5 updates 1.0 MTransaction Summary============================================================================================================================================ Upgrade 3 Packages (+4 Dependent packages)Total size: 3.0 MTotal download size: 2.2 MDownloading packages:No Presto metadata available for base(1/3): device-mapper-persistent-data-0.5.5-1.el7.x86_64.rpm | 350 kB 00:00:00(2/3): lvm2-2.02.130-5.el7_2.5.x86_64.rpm | 1.0 MB 00:00:00(3/3): lvm2-libs-2.02.130-5.el7_2.5.x86_64.rpm | 873 kB 00:00:11--------------------------------------------------------------------------------------------------------------------------------------------Total 195 kB/s | 2.2 MB 00:00:11Running transaction checkRunning transaction testTransaction test succeededRunning transactionUpdating : 7:device-mapper-1.02.107-5.el7_2.5.x86_64 1/14Updating : 7:device-mapper-libs-1.02.107-5.el7_2.5.x86_64 2/14Updating : 7:device-mapper-event-libs-1.02.107-5.el7_2.5.x86_64 3/14Updating : 7:device-mapper-event-1.02.107-5.el7_2.5.x86_64 4/14Updating : 7:lvm2-libs-2.02.130-5.el7_2.5.x86_64 5/14Updating : device-mapper-persistent-data-0.5.5-1.el7.x86_64 6/14Updating : 7:lvm2-2.02.130-5.el7_2.5.x86_64 7/14ln -s '/usr/lib/systemd/system/lvm2-lvmetad.socket''/etc/systemd/system/sysinit.target.wants/lvm2-lvmetad.socket'ln -s '/usr/lib/systemd/system/lvm2-lvmpolld.socket''/etc/systemd/system/sysinit.target.wants/lvm2-lvmpolld.socket'Cleanup : 7:lvm2-2.02.105-14.el7.x86_64 8/14Cleanup : 7:lvm2-libs-2.02.105-14.el7.x86_64 9/14Cleanup : 7:device-mapper-event-1.02.84-14.el7.x86_64 10/14Cleanup : 7:device-mapper-event-libs-1.02.84-14.el7.x86_64 11/14Cleanup : 7:device-mapper-1.02.84-14.el7.x86_64 12/14Cleanup : 7:device-mapper-libs-1.02.84-14.el7.x86_64 13/14Cleanup : device-mapper-persistent-data-0.3.2-1.el7.x86_64 14/14Verifying : 7:device-mapper-libs-1.02.107-5.el7_2.5.x86_64 1/14Verifying : 7:device-mapper-1.02.107-5.el7_2.5.x86_64 2/14Verifying : 7:lvm2-2.02.130-5.el7_2.5.x86_64 3/14Verifying : device-mapper-persistent-data-0.5.5-1.el7.x86_64 4/14Verifying : 7:lvm2-libs-2.02.130-5.el7_2.5.x86_64 5/14Verifying : 7:device-mapper-event-libs-1.02.107-5.el7_2.5.x86_64 6/14Verifying : 7:device-mapper-event-1.02.107-5.el7_2.5.x86_64 7/14Verifying : 7:lvm2-2.02.105-14.el7.x86_64 8/14Verifying : device-mapper-persistent-data-0.3.2-1.el7.x86_64 9/14Verifying : 7:lvm2-libs-2.02.105-14.el7.x86_64 10/14Verifying : 7:device-mapper-event-libs-1.02.84-14.el7.x86_64 11/14Verifying : 7:device-mapper-libs-1.02.84-14.el7.x86_64 12/14Verifying : 7:device-mapper-event-1.02.84-14.el7.x86_64 13/14Verifying : 7:device-mapper-1.02.84-14.el7.x86_64 14/14Updated:device-mapper-event-libs.x86_64 7:1.02.107-5.el7_2.5 device-mapper-libs.x86_64 7:1.02.107-5.el7_2.5 lvm2-libs.x86_64 7:2.02.130-5.el7_2.5 Dependency Updated:device-mapper.x86_64 7:1.02.107-5.el7_2.5 device-mapper-event.x86_64 7:1.02.107-5.el7_2.5device-mapper-persistent-data.x86_64 0:0.5.5-1.el7 lvm2.x86_64 7:2.02.130-5.el7_2.5Complete!继续docker安装－> 成功[root@localhost run]# yum install dockerLoaded plugins: fastestmirror, langpacksLoading mirror speeds from cached hostfile* base: * extras: * updates: Resolving Dependencies--> Running transaction check---> Package docker.x86_64 0:1.10.3-44.el7.centos will be installed--> Processing Dependency: oci-systemd-hook = 1.10.3-44.el7.centos for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: oci-register-machine = 1.10.3-44.el7.centos for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: docker-forward-journald = 1.10.3-44.el7.centos for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: docker-common = 1.10.3-44.el7.centos for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: selinux-policy >= 3.13.1-23for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: docker-selinux >= 1.10.3-44.el7.centos for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: libsystemd.so.0(LIBSYSTEMD_209)(64bit) for package: docker-1.10.3-44.el7.centos.x86_64--> Processing Dependency: libsystemd.so.0()(64bit) for package: docker-1.10.3-44.el7.centos.x86_64--> Running transaction check---> Package docker-common.x86_64 0:1.10.3-44.el7.centos will be installed---> Package docker-forward-journald.x86_64 0:1.10.3-44.el7.centos will be installed---> Package docker-selinux.x86_64 0:1.10.3-44.el7.centos will be installed--> Processing Dependency: selinux-policy-targeted >= 3.13.1-23for package: docker-selinux-1.10.3-44.el7.centos.x86_64--> Processing Dependency: selinux-policy-base >= 3.13.1-23for package: docker-selinux-1.10.3-44.el7.centos.x86_64---> Package oci-register-machine.x86_64 0:1.10.3-44.el7.centos will be installed---> Package oci-systemd-hook.x86_64 0:1.10.3-44.el7.centos will be installed---> Package selinux-policy.noarch 0:3.12.1-153.el7 will be updated---> Package selinux-policy.noarch 0:3.13.1-60.el7_2.7 will be an update---> Package systemd-libs.x86_64 0:208-11.el7 will be updated--> Processing Dependency: systemd-libs = 208-11.el7 for package: systemd-208-11.el7.x86_64---> Package systemd-libs.x86_64 0:219-19.el7_2.11 will be an update--> Running transaction check---> Package selinux-policy-targeted.noarch 0:3.12.1-153.el7 will be updated---> Package selinux-policy-targeted.noarch 0:3.13.1-60.el7_2.7 will be an update---> Package systemd.x86_64 0:208-11.el7 will be updated--> Processing Dependency: systemd = 208-11.el7 for package: libgudev1-208-11.el7.x86_64--> Processing Dependency: systemd = 208-11.el7 for package: systemd-python-208-11.el7.x86_64--> Processing Dependency: systemd = 208-11.el7 for package: systemd-sysv-208-11.el7.x86_64---> Package systemd.x86_64 0:219-19.el7_2.11 will be an update--> Processing Dependency: kmod >= 18-4for package: systemd-219-19.el7_2.11.x86_64--> Running transaction check---> Package kmod.x86_64 0:14-9.el7 will be updated---> Package kmod.x86_64 0:20-5.el7 will be an update---> Package libgudev1.x86_64 0:208-11.el7 will be updated---> Package libgudev1.x86_64 0:219-19.el7_2.11 will be an update---> Package systemd-python.x86_64 0:208-11.el7 will be updated---> Package systemd-python.x86_64 0:219-19.el7_2.11 will be an update---> Package systemd-sysv.x86_64 0:208-11.el7 will be updated---> Package systemd-sysv.x86_64 0:219-19.el7_2.11 will be an update--> Processing Conflict: systemd-219-19.el7_2.11.x86_64 conflicts initscripts < 9.49.28-1--> Restarting Dependency Resolution with new changes.--> Running transaction check---> Package initscripts.x86_64 0:9.49.17-1.el7 will be updated---> Package initscripts.x86_64 0:9.49.30-1.el7_2.2 will be an update--> Processing Conflict: systemd-219-19.el7_2.11.x86_64 conflicts dracut < 033-243--> Restarting Dependency Resolution with new changes.--> Running transaction check---> Package dracut.x86_64 0:033-161.el7 will be updated--> Processing Dependency: dracut = 033-161.el7 for package: dracut-config-rescue-033-161.el7.x86_64--> Processing Dependency: dracut = 033-161.el7 for package: dracut-network-033-161.el7.x86_64---> Package dracut.x86_64 0:033-360.el7_2.1 will be an update--> Running transaction check---> Package dracut-config-rescue.x86_64 0:033-161.el7 will be updated---> Package dracut-config-rescue.x86_64 0:033-360.el7_2.1 will be an update---> Package dracut-network.x86_64 0:033-161.el7 will be updated---> Package dracut-network.x86_64 0:033-360.el7_2.1 will be an update--> Finished Dependency ResolutionDependencies Resolved============================================================================================================================================ Package Arch Version Repository Size============================================================================================================================================ Installing:docker x86_64 1.10.3-44.el7.centos extras 8.6 MUpdating:dracut x86_64 033-360.el7_2.1 updates 311 kinitscripts x86_64 9.49.30-1.el7_2.2 updates 429 kInstalling for dependencies:docker-common x86_64 1.10.3-44.el7.centos extras 59 kdocker-forward-journald x86_64 1.10.3-44.el7.centos extras 831 kdocker-selinux x86_64 1.10.3-44.el7.centos extras 77 koci-register-machine x86_64 1.10.3-44.el7.centos extras 1.0 Moci-systemd-hook x86_64 1.10.3-44.el7.centos extras 96 kUpdating for dependencies:dracut-config-rescue x86_64 033-360.el7_2.1 updates 50 kdracut-network x86_64 033-360.el7_2.1 updates 90 kkmod x86_64 20-5.el7 base114 klibgudev1 x86_64 219-19.el7_2.11 updates 66 kselinux-policy noarch 3.13.1-60.el7_2.7 updates 376 kselinux-policy-targeted noarch 3.13.1-60.el7_2.7 updates 3.9 Msystemd x86_64 219-19.el7_2.11 updates 5.1 Msystemd-libs x86_64 219-19.el7_2.11 updates 358 ksystemd-python x86_64 219-19.el7_2.11 updates 99 ksystemd-sysv x86_64 219-19.el7_2.11 updates 53 kTransaction Summary============================================================================================================================================ Install 1 Package (+ 5 Dependent packages)Upgrade 2 Packages (+10 Dependent packages)Total size: 22 MIs this ok [y/d/N]: yDownloading packages:Running transaction checkRunning transaction testTransaction test succeededRunning transactionUpdating : systemd-libs-219-19.el7_2.11.x86_64 1/30Updating : dracut-033-360.el7_2.1.x86_64 2/30Updating : kmod-20-5.el7.x86_64 3/30Updating : systemd-219-19.el7_2.11.x86_64 4/30Updating : selinux-policy-3.13.1-60.el7_2.7.noarch 5/30Updating : selinux-policy-targeted-3.13.1-60.el7_2.7.noarch 6/30140kInstalling : docker-selinux-1.10.3-44.el7.centos.x86_64 7/30Installing : oci-register-machine-1.10.3-44.el7.centos.x86_64 8/30Installing : docker-forward-journald-1.10.3-44.el7.centos.x86_64 9/30Installing : docker-common-1.10.3-44.el7.centos.x86_64 10/30Installing : oci-systemd-hook-1.10.3-44.el7.centos.x86_64 11/30Installing : docker-1.10.3-44.el7.centos.x86_64 12/30Updating : initscripts-9.49.30-1.el7_2.2.x86_64 13/30Updating : systemd-sysv-219-19.el7_2.11.x86_64 14/30Updating : systemd-python-219-19.el7_2.11.x86_64 15/30Updating : dracut-config-rescue-033-360.el7_2.1.x86_64 16/30Updating : dracut-network-033-360.el7_2.1.x86_64 17/30Updating : libgudev1-219-19.el7_2.11.x86_64 18/30Cleanup : selinux-policy-targeted-3.12.1-153.el7.noarch 19/30warning: file /etc/selinux/targeted/modules/active/modules/vbetool.pp: remove failed: No such file or directorywarning: file /etc/selinux/targeted/modules/active/modules/pkcsslotd.pp: remove failed: No such file or directoryCleanup : systemd-sysv-208-11.el7.x86_64 20/30Cleanup : dracut-network-033-161.el7.x86_64 21/30Cleanup : dracut-config-rescue-033-161.el7.x86_64 22/30Cleanup : dracut-033-161.el7.x86_64 23/30Cleanup : systemd-python-208-11.el7.x86_64 24/30Cleanup : libgudev1-208-11.el7.x86_64 25/30Cleanup : initscripts-9.49.17-1.el7.x86_64 26/30Cleanup : selinux-policy-3.12.1-153.el7.noarch 27/30Cleanup : systemd-208-11.el7.x86_64 28/30Cleanup : kmod-14-9.el7.x86_64 29/30Cleanup : systemd-libs-208-11.el7.x86_64 30/30Verifying : dracut-config-rescue-033-360.el7_2.1.x86_64 1/30Verifying : initscripts-9.49.30-1.el7_2.2.x86_64 2/30Verifying : dracut-network-033-360.el7_2.1.x86_64 3/30Verifying : oci-systemd-hook-1.10.3-44.el7.centos.x86_64 4/30Verifying : kmod-20-5.el7.x86_64 5/30Verifying : libgudev1-219-19.el7_2.11.x86_64 6/30Verifying : selinux-policy-3.13.1-60.el7_2.7.noarch 7/30Verifying : docker-selinux-1.10.3-44.el7.centos.x86_64 8/30Verifying : systemd-libs-219-19.el7_2.11.x86_64 9/30Verifying : dracut-033-360.el7_2.1.x86_64 10/30Verifying : systemd-219-19.el7_2.11.x86_64 11/30Verifying : docker-common-1.10.3-44.el7.centos.x86_64 12/30Verifying : docker-1.10.3-44.el7.centos.x86_64 13/30Verifying : systemd-sysv-219-19.el7_2.11.x86_64 14/30Verifying : docker-forward-journald-1.10.3-44.el7.centos.x86_64 15/30Verifying : systemd-python-219-19.el7_2.11.x86_64 16/30。
使用Docker容器构建AI模型部署环境的方法与技巧
使用Docker容器构建AI模型部署环境的方法与技巧随着人工智能技术的发展，AI模型的构建和部署越来越成为热门话题。
而Docker作为一个流行的容器化解决方案，为AI模型的部署提供了便捷和灵活性。
本文将介绍使用Docker容器构建AI模型部署环境的方法与技巧。
1. 安装DockerDocker可以在各个操作系统上进行安装，包括Windows、Mac和Linux。
在安装Docker之前，需要确保操作系统符合最低要求，并且关闭其他应用程序，以避免冲突。
安装完成后，通过命令行输入"docker --version"来验证安装是否成功。
2. 构建Docker镜像Docker镜像是Docker容器的基础，包含了运行环境和所需的依赖项。
对于AI模型的部署，可以选择从已有的镜像构建或者自己编写Dockerfile。
如果选择从已有的镜像构建，可以在Docker Hub上搜索适合的镜像，如tensorflow、pytorch等。
通过命令行输入"docker pull [镜像名称]"来下载所需镜像。
如果选择自己编写Dockerfile，可以在文件中定义所需的环境和依赖项，并通过命令行输入"docker build -t [镜像名称] [Dockerfile路径]"来构建镜像。
3. 运行Docker容器构建完成Docker镜像后，可以通过命令行输入"docker run -d -p [主机端口]:[容器端口] [镜像名称]"来运行Docker容器。
其中，-d参数用于在后台运行容器，-p参数用于指定主机端口和容器端口的映射关系。
运行容器后，可以通过访问主机端口来使用AI模型。
4. 部署AI模型在Docker容器中部署AI模型可以根据具体需求选择不同的方法。
一种常见的方法是将训练好的模型加载到容器中，并提供API接口来供其他应用程序调用。
可以使用框架自带的API工具，如TensorFlow serving或FastAPI。
docker安装java环境的实现步骤
docker安装java环境的实现步骤本⽂是基于Linux centos8安装docker后再拉取镜像安装各个环境(tomcat,mysql,redis等等)docker安装tomcat下载tomcat(可以指定版本号,这⾥默认安装最新的版本哈,指定版本号⽰例 docker pull tomcat:9.0.37 )[root@localhost ~]# docker pull tomcat:9.0.37启动[root@localhost ~]# docker run -d -p 8080:8080 --name tomcat01 tomcat(阿⾥的某些容器,如tomcat的镜像的webapp⽂件夹是空的,在webapps.dist⾥⾯,所以注意要将webapps.dist⽂件复制到webapps的⽬录),如图所⽰#进⼊容器⽬录[root@localhost ~]# docker exec -it tomcat01 /bin/bash#切换到webapps.dist⽂件夹root@77e211d23175:/usr/local/tomcat# cd webapps.dist#复制⽂件root@77e211d23175:/usr/local/tomcat# cp -r webapps.dist/* webapps这⾥顺便可以把修改后的tomcat作为⼀个新的容器,以免下⼀次再复制⽂件(e8c58b381b99 是tomcat容器id)[root@localhost ~]# docker commit -m="完善webapps应有的⽂件" -a="张晓祥" e8c58b381b99 tomcat01:9.0.37Docker安装Elasticsearch下载镜像[root@localhost ~]# docker pull elasticsearch:7.9.0创建⽹络,就是起个名字,如esnet[root@localhost ~]# docker network create esnet单节点运⾏(没有配置集群)[root@localhost ~]# docker run -d --name elasticsearch --net esnet -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" elasticsearch:7.9.0查看是否运⾏成功(如果还在启动会报 curl: (56) Recv failure: 连接被对⽅重设),当然也可以使⽤浏览器测试(注意把防⽕墙关闭了)[root@localhost ~]# curl localhost:9200启动成功返回⽰例docker安装mysql下载镜像[root@localhost dcoekrdata]# docker pull mysql:8.0.21运⾏(-d后台运⾏,-v数据挂载 -e环境配置)[root@localhost dcoekrdata]# docker run -d -p 3306:3306 -v /home/dockerdata/mysql/conf:/etc/mysql/conf.d -v /home/dockerdata/mysql/data:/var/lib/mysql -e MYSQL_ROOT_PASSWORD=root --name root mysql:8.0.21使⽤Navicat测试⼀下即可.docker安装RocketMq注意这个需要安装3个镜像才算OK哈,参考⽂档1:安装mq[root@localhost dcoekrdata]# docker pull rocketmqinc/rocketmq:4.3.2运⾏mq服务器docker run -d -p 9876:9876 -v /home/dockerdata/mq/namesrv/logs:/root/logs -v /home/dockerdata/mq/namesrv/store:/root/store --name rmqnamesrv -e "MAX_POSSIBLE_HEAP=100000000" rocketmqinc/rocketmq:4.3.2 sh mqnamesrv2:安装broker[root@localhost dcoekrdata]# docker pull rocketmqinc/rocketmq-broker:4.5.0-alpine-uid配置broker[root@localhost dcoekrdata]# cd /home/dockerdata/mq[root@localhost mq]# mkdir broker[root@localhost mq]# cd broker/[root@localhost broker]# touch broker.conf[root@localhost broker]# vi broker.conf配置⽂件(brokerIP1 =192.168.32.128是云服务器的公⽹IP,或者虚拟机Linux的IP,本⽂只是我的⽰例)terName = DefaultClusterbrokerName = broker-abrokerId = 0deleteWhen = 04fileReservedTime = 48brokerRole = ASYNC_MASTERflushDiskType = ASYNC_FLUSHbrokerIP1 =192.168.32.128启动brokerdocker run -d -p 10911:10911 -p 10909:10909 -v /home/dockerdata/mq/broker/logs:/root/logs -v /home/dockerdata/mq/broker/store:/root/store -v /home/dockerdata/mq/broker/broker.conf:/opt/rocketmq-4.3.2/conf/broker.conf --name rmqbroker --link rmqnamesrv:n 3:安装控制台rocketmq-console-ng[root@localhost broker]# docker pull styletang/rocketmq-console-ng:1.0.0启动控制台(注意IP地址)[root@localhost broker]# docker run -e "JAVA_OPTS=srv.addr=192.168.32.128:9876 -Dcom.rocketmq.sendMessageWithVIPChannel=false" -p 8080:8080 -t styletang/rocketmq-console-ng:1.0.0安装成功,测试如图到此这篇关于docker安装java环境的实现步骤的⽂章就介绍到这了,更多相关docker安装java环境内容请搜索以前的⽂章或继续浏览下⾯的相关⽂章希望⼤家以后多多⽀持！。
如何使用Docker容器构建大规模游戏服务器
如何使用Docker容器构建大规模游戏服务器随着游戏产业的迅猛发展，大规模游戏服务器的搭建和部署成为游戏开发者面临的重要任务之一。
在传统的服务器架构中，配置和管理各种依赖项和组件可能变得繁琐且复杂。
然而，使用Docker容器可以极大地简化这一任务，并提供可靠且可伸缩的解决方案。
本文将介绍如何使用Docker容器构建大规模游戏服务器的步骤和最佳实践。
步骤一：安装Docker首先，需要在目标服务器上安装Docker。
Docker是一个开源平台，可以轻松构建、测试和部署应用程序。
在Linux服务器上，可以使用包管理器（如apt或yum）来安装Docker。
安装完成后，可以通过运行docker --version命令来验证安装是否成功。
步骤二：创建Docker镜像下一步是创建游戏服务器的Docker镜像。
Docker镜像是一个轻量级、可移植的打包文件，其中包含了运行游戏服务器所需的所有依赖项和配置。
可以使用Dockerfile来定义如何构建镜像。
以下是一个基本的Dockerfile示例：```FROM baseimageCOPY . /appWORKDIR /appRUN npm installCMD ["npm", "start"]```在这个示例中，我们使用baseimage作为基础镜像，并将游戏服务器的源代码复制到/app目录下。
然后通过运行npm install命令来安装依赖项，并最后运行npm start命令来启动游戏服务器。
步骤三：构建Docker镜像一旦Dockerfile定义完成，可以使用docker build命令来构建镜像。
以下是构建镜像的命令示例：```docker build -t game-server .```这个命令将根据当前目录中的Dockerfile构建一个名为game-server的镜像。
期间Docker会自动下载和安装所需的依赖项，并在构建完成后生成一个可用的Docker镜像。
银河麒麟服务器操作系统-Docker适配手册
银河麒麟服务器操作系统D ocker软件适配手册目录1概述 (2)1.1系统概述 (2)1.2环境概述 (2)1.3DOCKER及相关软件简介 (2)1.4架构及原理 (2)1.4.1优点 (4)2使用方法 (4)1)安装DOCKER及相关软件 (4)2)设置开机自启动并启动DOCKER-CE (4)3)DOCKER容器使用 (5)3.1DOCKER客户端 (5)3.2运行一个应用 (5)3.3查看应用容器 (5)3.4网络端口的快捷方式 (6)3.5查看应用程序日志 (6)3.6查看应用程序容器的进程 (6)3.7检查应用程序 (7)3.8停止应用容器 (8)3.9重启应用容器 (8)3.10移除应用容器 (8)4)DOCKER容器连接 (8)1.1网络端口映射 (9)1.2DOCKER容器连接 (10)1.2.1容器命名 (10)5)DOCKER镜像使用 (10)3.1列出镜像列表 (10)3.2获取一个新的镜像 (11)3.3查找镜像 (12)3.4创建镜像 (12)3.5更新镜像 (12)1概述1.1系统概述银河麒麟服务器操作系统主要面向军队综合电子信息系统、金融系统以及电力系统等国家关键行业的服务器应用领域，突出高安全性、高可用性、高效数据处理、虚拟化等关键技术优势，针对关键业务构建的丰富高效、安全可靠的功能特性，兼容适配长城、联想、浪潮、华为、曙光等国内主流厂商的服务器整机产品，以及达梦、金仓、神通、南大通用等主要国产数据库和中创、金蝶、东方通等国产中间件，满足虚拟化、云计算和大数据时代，服务器业务对操作系统在性能、安全性及可扩展性等方面的需求，是一款具有高安全、高可用、高可靠、高性能的自主可控服务器操作系统。
1.2环境概述服务器型号长城信安擎天DF720服务器CPU类型飞腾2000+处理器操作系统版本Kylin-4.0.2-server-sp2-2000-19050910.Z1内核版本 4.4.131docker版本18.06.1~ce1.3docker及相关软件简介Docker是一个开源的应用容器引擎，基于Go语言并遵从Apache2.0协议开源。
docker学习笔记
docker学习笔记DockerDocker基础Docker概述Docker 平台的基本构成Docker安装环境准备1、需要会⼀点点Linux基础2、CentOS 73、Xshell 或者其它远程连接⼯具环境查看# 查看系统内核, 要求版本>3.10uname -r3.10.0-1062.12.1.el7.x86_64# 查看系统版本等相关信息cat /etc/os-release安装帮助⽂档:# 1. 卸载旧的版本yum remove docker \docker-client \docker-client-latest \docker-common \docker-latest \docker-latest-logrotate \docker-engine# 2. 安装依赖包yum install -y yum-untils# 3. 设置镜像仓库yum-config-manager \--add-repo \https:///linux/centos/docker-ce.repo # 默认国外的镜像仓库yum-config-manager \--add-repo \https:///docker-ce/linux/centos/docker-ce.repo # 阿⾥云的镜像仓库(推荐)# 更新yum软件包索引yum makecache fast# 4. 安装Docker相关, docker-ce 社区版 docker-ee 企业版yum install docker-ce docker-ce-cli containerd.io# 安装指定版本yum install docker-ce-<VERSION-STRING> docker-ce-cli-<VERSION-STRING> container.io# 5. 启动Dockersystemctl start docker# 6. 使⽤docker version查看是否安装成功docker version# 7. 测试 HelloWorld!docker run hello-world# 8. 查看已下载的镜像docker imagesREPOSITORY TAG IMAGE ID CREATED SIZEhello-world latest d1165f221234 5 months ago 13.3kB卸载docker# 1. 卸载依赖yum remove docker-ce docker-ce-cli containerd.io# 2. 删除资源rm -rf /var/lib/docker # Docker的默认⼯作资源路径安装-2RedHat/CentOS必须要6.6版本以上，或者7.x才能安装docker，建议在RedHat/CentOS 7上使⽤docker，因为RedHat/CentOS 7的内核升级到了kernel 3.10，对lxc容器⽀持更好。
ABLOOMY 协作云服务平台操作手册（针对阿里云软件服务盒子）说明书
ABLOOMY协作云服务平台操作手册针对阿里云软件服务盒子文档版本：V1.0发布时间：2020.07.10韵盛发科技（北京）股份有限公司版权声明：版权所有© 2019 韵盛发科技（北京）股份有限公司，保留一切权利。
未经过韵盛发科技（北京）股份有限公司（以下简称“ABLOOMY”）书面许可，任何人不得以任何方式或形式对本文档内和其中所包含的任何资料进行复制、摘录、备份、传播或翻译成其他语言，不得将其全部或部分用于商业用途。
商标：是韵盛发科技（北京）股份有限公司(“ABLOOMY”)的注册商标。
本手册中所有其他注册的或未注册的商标，由各自权利人拥有。
免责声明：您购买的产品、服务或特性等应受ABLOOMY商业合同和条款的约束，本文档中描述的全部或部分产品、服务或特性可能不在您的购买或使用范围之内。
除非合同另有约定，ABLOOMY对本文档内容不做任何明示或默示的声明或保证。
由于产品版本升级或其他原因，本文档内容会不定期进行更新。
除非另有约定，本文档仅作为使用指导，本文档中的所有陈述、信息和建议不构成任何明示或暗示的担保。
技术支持：邮箱：*********************.cn热线电话：400-010-6602更多详情：关注ABLOOMY官方微信abloomy-china网站：目录第1章引言 (1)1.1简介 (1)1.2文档目的 (1)第2章软件服务盒子的购买 (3)2.1阿里云云市场下单购买 (3)第3章软件服务盒子安装 (6)3.1环境准备 (7)3.2登录协作平台 (7)3.3软件服务盒子安装 (8)3.3.1Docker环境部署 (8)3.3.2安装与激活 (9)第4章添加资产与管理 (14)4.1资产导入 (14)4.1.1扫描导入资产 (14)4.1.2爱菠萝App扫描资产 (14)4.1.3WEB平台添加主机资产 (16)4.2主机管理 (19)4.2.1管理员授权模式 (19)4.2.2自动授权模式 (22)4.2.3手工登录 (22)第5章设备运维场景 (23)5.1环境准备 (23)5.2基本流程 (23)5.2.1下载Abloomy爱菠萝App (23)5.2.2安装服务盒子 (24)5.2.3添加运维主机 (24)5.2.4添加支持人员 (24)5.2.5创建运维事件 (24)5.2.6工程师/代理商接单 (29)5.2.7沟通讨论 (30)5.2.8确认签订合同 (32)5.2.9处理/完成运维事件 (36)第6章创建密码箱口令 (41)第7章协作平台添加好友 (44)第8章虚拟实验室 (45)8.1创建白板 (45)8.2搭建实验环境 (45)8.3激活虚拟实验室 (46)8.4完成实验关闭虚拟实验室 (48)第9章主机监控功能设置 (49)9.1自动监控功能 (49)9.2SNMP网络设备自动监控 (49)9.2.1模板导入 (49)9.2.2开启自动监控 (50)9.2.3关闭自动监控 (52)9.3Agent服务器自动监控 (53)9.3.1Windows安装Agent (53)9.3.2Linux安装Agent (56)9.3.3Agent配置 (57)第10章组织 (58)10.1用户管理 (58)10.2组织管理 (58)第1章引言1.1简介软件服务盒子是Abloomy 针对于IT云堡垒运维服务推出的软件版服务盒子，适合部署在企业IT网络环境中，供IT工程师远程运维使用。
Linux安装Pytorch1.8GPU（CUDA11.1）的实现
Linux安装Pytorch1.8GPU（CUDA11.1）的实现先说下⾃⼰之前的环境（都是Linux系统，差别不⼤）：Centos7.6NVIDIA Driver Version 440.33.01（等会需要更新驱动）CUDA10.1Pytorch1.6/1.7提⽰，如果想要保留之前的PyTorch1.6或1.7的环境，请不要卸载CUDA环境，可以通过Anaconda管理不同的环境，互不影响。
但是需要注意你的NVIDIA驱动版本是否匹配。
在这⾥能够看到官⽅给的对应CUDA版本所需使⽤驱动版本。
通过上表可以发现，如果要使⽤CUDA11.1，那么需要将显卡的驱动更新⾄455.23或以上（Linux x86_64环境）。
由于我之前的驱动版本是440.33.01，那么肯定不满⾜，所以需要更新下显卡的驱动。
通过以下指令可以查看你电脑上的驱动版本：nvidia-smi如果你的驱动版本是满⾜的，那么可以直接跳到创建Pytorch1.8虚拟环境章节。
更新驱动卸载旧驱动我之前安装的是NVIDIA-440的版本，找到之前下载的安装程序，然后打开终端通过以下指令进⾏卸载：sh ./NVIDIA-Linux-x86_64-440.33.01.run --uninstall安装新驱动根据你的GPU型号以及操作信息选择对应的驱动，注意CUDA Toolkit11版的当前可选的只有11.0和11.2，⽽我们要装的是11.1所以选择11.2即可。
2）关闭Xserver服务（如果没有安装桌⾯系统可以跳过）我的桌⾯系统是gdm（GNOME Display Manager）类型的，通过systemctl可以看到：systemctl status gdm.service显⽰结果：● gdm.service - GNOME Display ManagerLoaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: enabled)Active: active (running) since Fri 2021-01-22 09:27:06 CST; 1 months 22 days agoProcess: 32347 ExecStartPost=/bin/bash -c TERM=linux /usr/bin/clear > /dev/tty1 (code=exited, status=0/SUCCESS)Main PID: 32344 (gdm)Tasks: 22CGroup: /system.slice/gdm.service├─32344 /usr/sbin/gdm└─32357 /usr/bin/X :0 -background none -noreset -audit 4 -verbose -auth /run/gdm/auth-for-gdm-mBzawN/databa...Jan 22 09:27:06 localhost.localdomain systemd[1]: Starting GNOME Display Manager...Jan 22 09:27:06 localhost.localdomain systemd[1]: Started GNOME Display Manager.关闭gdm服务：systemctl stop gdm.service注意，如果还开启了类似VNC远程桌⾯的服务也要记得关闭。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
1、ubuntu下docker安装
sudo apt-get install docker.io
2、检查是否安装成功
docker.io version
3、下载镜像
docker.io pull centos:7
4、查看镜像
docker.io images
5、交互运行运行镜像
sudo docker.io run -i -t centos /bin/bash
启动容器
sudo docker.io 容器名称或者容器id
crtl+P+Q 退出容器，不关闭容器
sudo docker.io exec -it 46b7633592ea /bin/bash
6、crtl+D 退出交互模式
7、进入运行的容器
docker.io attach 46b7633592ea
8、从容器内拷贝文件到主机
1. docker cp
9、从主机拷贝到容器内
先查找容器的全id
sudo docker.io inspect -f '{{.Id}}' 46b7633592ea
然后拷贝
进入cd
/var/lib/docker/aufs/mnt/46b7633592eaac2dd997e3717500f9ff114f8ba70ded
9b97fd4a1b3975d70cec/jvm
执行sudo mv /home/kfpt/nifi-1.3.0-bin.zip ./
10、生成镜像
sudo docker.io commit 46b7633592ea jdk
11、保存镜像
sudo docker.io save -o /home/kfpt/jdk1023.tar jdk
12、下载镜像
sudo docker.io load -i /home/kfpt/jdk1023.tar
或者docker.io load < /home/kfpt/ jdk1023.tar
13、sudo docker.io bulid greatsoft/nifi