Docker 卡在 Waiting for SSH to be available和 Error running apt-get update报错的处理

最新推荐文章于 2023-03-10 17:05:43 发布
最新推荐文章于 2023-03-10 17:05:43 发布
阅读量1.3k 收藏 1
点赞数
文章标签： linux docker
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/ringwater/article/details/123785530
版权

问题原因：

ringwater@ubuntu:~$ docker-machine create --driver generic --generic-ip-address=10.0.8.11 host1
Running pre-create checks...
Creating machine...
(host1) No SSH key specified. Assuming an existing key at the default location.
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...

管理的主机没有启用root，并且要开启ssh的root登录。

解决方法：

一、在安装docker machine的主机使用root登录并生成ssh-genkey 

，并使用 ssh-copy-id考虑公钥到需要管理的主机 

二、需要的管理主机上进行以下配置：

1 ）允许root用户登录；编辑配置文件：

sudo vim /etc/ssh/sshd_config
PermitRootLogin prohibit-password

更改为：

PermitRootLogin yes

重启ssh服务：

sudo systemctl restart sshd

2) 创建密钥对（machine主机操作）

# ssh-keygen #一直回车

三、在安装docker machine的主机上使用命令进行管理

root@ubuntu:~# docker-machine create --driver generic --generic-ip-address=10.0.8.11 host1
Running pre-create checks...
Creating machine...
(host1) No SSH key specified. Assuming an existing key at the default location.
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...#已经没有报错了
Detecting the provisioner...
Provisioning with ubuntu(systemd)...

。。。。。。

四、ssh已经没有问题，继续对报错进行处理：

root@ubuntu:~# docker-machine create --driver generic --generic-ip-address=10.0.8.11 host1
Running pre-create checks...
Creating machine...
(host1) No SSH key specified. Assuming an existing key at the default location.
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with ubuntu(systemd)...
Error creating machine: Error running provisioning: Error running apt-get update: ssh command error:
command : sudo apt-get update
err     : exit status 100
output  : Ign:1 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial InRelease
Ign:2 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial Release
Ign:3 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main amd64 Packages
Ign:4 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main i386 Packages
Ign:5 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main all Packages
Ign:6 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main Translation-en_US
Ign:7 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main Translation-en
Ign:8 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted amd64 Packages
Ign:9 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted i386 Packages
Ign:10 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted all Packages
Ign:11 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted Translation-en_US
Ign:12 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted Translation-en
Ign:3 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main amd64 Packages
Ign:4 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main i386 Packages
Ign:5 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main all Packages
Ign:6 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main Translation-en_US
Ign:7 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main Translation-en
Ign:8 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted amd64 Packages
Ign:9 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted i386 Packages
Ign:10 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted all Packages
Ign:11 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted Translation-en_US
Ign:12 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted Translation-en
Ign:3 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main amd64 Packages
Ign:4 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main i386 Packages
Ign:5 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main all Packages
Ign:6 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main Translation-en_US
Ign:7 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main Translation-en
Ign:8 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted amd64 Packages
Ign:9 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted i386 Packages
Ign:10 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted all Packages
Ign:11 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted Translation-en_US
Ign:12 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted Translation-en
Ign:3 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main amd64 Packages
Ign:4 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main i386 Packages
Ign:5 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main all Packages
Ign:6 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main Translation-en_US
Ign:7 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main Translation-en
Ign:8 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted amd64 Packages
Ign:9 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted i386 Packages
Ign:10 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted all Packages
Ign:11 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted Translation-en_US
Ign:12 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted Translation-en
Ign:3 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main amd64 Packages
Ign:4 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main i386 Packages
Ign:5 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main all Packages
Ign:6 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main Translation-en_US
Ign:7 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main Translation-en
Ign:8 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted amd64 Packages
Ign:9 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted i386 Packages
Ign:10 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted all Packages
Ign:11 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted Translation-en_US
Ign:12 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/restricted Translation-en
Err:3 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main amd64 Packages
  Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
Ign:4 cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial/main i386 Packages
Hit:13 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:14 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Hit:15 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:16 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Reading package lists...
W: The repository 'cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8) xenial Release' does not have a Release file.
E: Failed to fetch cdrom://Ubuntu-Server 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.8)/dists/xenial/main/binary-amd64/Packages  Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
E: Some index files failed to download. They have been ignored, or old ones used instead.

更新源为阿里云的源：

$ sudo su -     # 切换到 root 目录

# cd /etc/apt/

# cp sources.list  sources.list.bak

# true> sources.list

# vi  /etc/apt/sources.list    # 将上面的源复制到文件中, 保存退出

deb-src http://archive.ubuntu.com/ubuntu xenial main restricted #Added by software-properties
deb http://mirrors.aliyun.com/ubuntu/ xenial main restricted
deb-src http://mirrors.aliyun.com/ubuntu/ xenial main restricted multiverse universe #Added by software-properties
deb http://mirrors.aliyun.com/ubuntu/ xenial-updates main restricted
deb-src http://mirrors.aliyun.com/ubuntu/ xenial-updates main restricted multiverse universe #Added by software-properties
deb http://mirrors.aliyun.com/ubuntu/ xenial universe
deb http://mirrors.aliyun.com/ubuntu/ xenial-updates universe
deb http://mirrors.aliyun.com/ubuntu/ xenial multiverse
deb http://mirrors.aliyun.com/ubuntu/ xenial-updates multiverse
deb http://mirrors.aliyun.com/ubuntu/ xenial-backports main restricted universe multiverse
deb-src http://mirrors.aliyun.com/ubuntu/ xenial-backports main restricted universe multiverse #Added by software-properties
deb http://archive.canonical.com/ubuntu xenial partner
deb-src http://archive.canonical.com/ubuntu xenial partner
deb http://mirrors.aliyun.com/ubuntu/ xenial-security main restricted
deb-src http://mirrors.aliyun.com/ubuntu/ xenial-security main restricted multiverse universe #Added by software-properties
deb http://mirrors.aliyun.com/ubuntu/ xenial-security universe
deb http://mirrors.aliyun.com/ubuntu/ xenial-security multiverse

# apt update    # 更新本地 apt 源

五、重新执行docker-machine create --driver generic --generic-ip-address=10.0.8.11 host1完成对host1的管理：

root@ubuntu:~# docker-machine create --driver generic --generic-ip-address=10.0.8.11 host1
Running pre-create checks...
Creating machine...
(host1) No SSH key specified. Assuming an existing key at the default location.
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with ubuntu(systemd)...
Installing Docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env host1

ringwater
关注
不使用K8S和Docker Swarm的情况下,纯Docker环境下nginx+hyperf+pm2的部署方案
jobsen123的专栏
07-16 3856
一 、构建Php镜像，其镜像包含pm2和pm2-logrotate以及ssh公钥登录功能 Dockerfile FROM ubuntu:18.04 MAINTAINER jobsen123@qq.com ENV DEBIAN_FRONTEND noninteractive RUN sed -i -e s@/archive.ubuntu.com/@/mirrors.aliyun.com/@g -e s@/security.ubuntu.com/@/mirrors.aliyun.com/@g /etc/.
Docker全方位攻略与自动化运维
dg313的博客
02-22 651
(Docker注册中心)是一个管理Docker容器镜像存储和交付的应用程序。注册中心集中容器镜像并减少开发人员的构建时间。Docker镜像通过虚拟化保证相同的运行环境，但是构建镜像需要大量的时间投入。例如，开发人员可以从包含所有必要组件的注册中心下载压缩镜像，而不是单独安装依赖项和包来使用Docker。Buddy自动将镜像推送到注册中心，以在生产和开发过程中无缝更新镜像。Docker Hub是一个免费公共的注册中心，可以托管您的自定义Docker镜像，但在某些情况下您不希望您的镜像公开使用。
Docker 卡在 Waiting for SSH to be available…
u011451803的博客
03-15 3652
不想看分析步骤，只想知道解决方法，可以直接跳转到解决方案 问题 本来跟着 Docker 官方文档 走，写几个例子当练手，结果在 part 4 的时候被卡住了。按照文档的要求在 Cmder 里执行命令 docker-machine create -d hyperv --hyperv-virtual-switch "myswitch" myvm1 ，一路上在 Hyper-V 新建虚拟机等等都没什么问题...
自己挖的坑自己填--docker创建实例出现Waiting for SSH to be available…
weixin_30535913的博客
08-16 510
在之前使用Docker for Windows Installer.exe直接安装，通过docker-machine-driver-vmwareworkstation.exe实现docker和VM的共存，而不必安装VirtualBox，但在安装VM后，为避免每次开机都把VM的服务全部自动开启，我把它们都改为“手动”开启，所以开机时状态都是关闭状态。 但在win10关机重启系统后: ...
Docker 容器无法联网 apt update 失败 解决
tiger_Angle
07-13 5269
第一种:重启docker第二种: 第三种:
Mac virtualbox k8s通过yaml创建pod_解决k8s无法通过svc访问其他节点pod的问题
Lambda
07-24 602
问题描述 有两个(或多个)运行在不同节点上的pod，通过一个svc提供服务，如下： root@master1:~# kubectl get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE kubia-nwjcc 1/1 Running 0 33m 1...
当docker pull mysql时，一直Waiting，很多等待，报：error pulling image configuration
weixin_42917368的博客
07-03 4万+
1、具体错内容：error pulling image configuration: Get https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/5c/5c62e459e087e3bd3d963092b58e50ae2af881076b43c29e38e2b5db253e0287/data?verify=1625273706-mWS9XIRfKs9FdV05eQJU1VqLc2U%3D: d
my cloud test bed (by quqi99)
技术并艺术着
03-10 1666
若容器里如果上不了网，如无法访问api.snapcraft.io，是因为lxd容易默认使用了eth1上的dns=10.10.10.1，下面的配置可让eth0, eth1, eth2都默认使用dns=192.168.99.1来避免特色网络对api.snapcraft.io的污染。下列netplan配置创建了br-eth0，也让br-eth0支持wol通过魔术包唤醒，也创建了一个没有dhcp的br-maas用于maas实验。
Longhorn 企业级云原生容器存储解决方案-部署篇
o__cc的博客
08-18 1272
内容来源于官方 Longhorn 1.1.2 英文技术手册。 系列 Longhorn 是什么? Longhorn 云原生分布式块存储解决方案设计架构和概念 安装 Longhorn 可以通过多种方式安装在 Kubernetes 集群上： Rancher catalog app kubectl Helm 安装要求 安装 Longhorn 的 Kubernetes 集群中的每个节点都必须满足...
Debian自动化安装
diezhong0234的博客
08-21 2635
定制Debian的自动化安装 1 更改grub配置文件，修改安装系统选项，加载安装配置文件（/boot/grub/grub.cfg） if loadfont $prefix/font.pf2 ; then set gfxmode=800x600 insmod efi_gop insmod efi_uga insmod video_bochs insmod video_...
用docker-machine创建虚拟主机
Jiuchen的博客
06-06 1528
环境 Window server 2012 R2 64 VMware Workstation 12 CentOS 7 创建虚拟主机 创建一个 oracle virtualbox 为驱动的虚拟主机，关于主机驱动可以参考官网：https://docs.docker.com/machine/drivers/ 这时创建时使用了一个阿里的加速器 --engine-registry-mirror h...
docker-machine create -d generic 运行的波折过程及遇见的问题
weixin_33889665的博客
01-04 497
这是一个愚蠢的学习过程，但是因为觉得过程还是值得记录的，还是写了下来 2》driver = generic 1)在这个过程中使用的都是本地的mac系统，然后尝试在mac本地create -d generic 一直不成功，出现下面的错误： Error creating machine: Error waiting for machine to be running: Maximum nu...
创建machine出错 Error detecting OS: Error getting SSH command: command:cat /etc/os-release
YICONGITSME的博客
08-17 3829
刚解决了安装machine的问题，又迎来一个问题，创建machine。 Host：ubuntu14.04 Kernel：4.4.0-31-generic Docker：18.06.0-ce Storage driver：overlay2 host1：ubuntu14.04 host2：Centos6.6 部署ubuntu时，很顺利就安装成功了。具体的步骤参考网上教程，我就不具体说...
docker-machine: Error creating machine: Error running provisioning: ssh command error
weixin_30341745的博客
12-21 1316
问题描述： 当我使用docker-machine安装docker到另一台电脑的时候，遇到这个问题： [felix@felix ~]$ docker-machine create --driver generic --generic-ssh-user felix --generic-ip-address=172.125.1.71 host1Running pre-create checks.....
PostgreSQL 启动失败解决方法
热门推荐
Cheers Li 软件测试博客
07-11 5万+
PostgreSQL 启动失败解决 机房断电了，PostgreSQL 起不起来了。 [root@scoder19 9.3]# service postgresql-9.3 start Starting postgresql-9.3 service: [FAILED] 日志文件（/var/lib/pgsql/9.3/pgstartup.log）：报错如下： FATAL:  data
Docker(五)：Docker 三剑客之 Docker Machine
weixin_34034670的博客
03-30 230
上篇文章Docker(四)：Docker 三剑客之 Docker Compose介绍了 Docker Compose，这篇文章我们来了解 Docker Machine 。 Docker Machine 介绍 Docker Machine 是 Docker 官方编排（Orchestration）项目之一，负责在多种平台上快速安装 Docker 环境。 Docker Machine 是一个工具，它允许...
【kubernetes/k8s概念】k8s 坑问题汇总
zhonglinzhang
12-26 3万+
1.Pod始终处于Pending状态 如果Pod保持在Pending的状态，意味着无法被正常的调度到节点上。由于某种系统资源无法满足Pod运行的需求 系统没有足够的资源：已经用尽了集群中所有的CPU或内存资源。需要清理一些不在需要的Pod，调整它们所需的资源量，或者向集群中增加新的节点。 用户指定了hostPort：通过hostPort用户能够将服务暴露到指定的主机端口上，会限......
docker apt-get update报错
最新发布
09-16
### 回答1： ...总之，在处理"apt-get update"命令报错时，需要仔细检查网络连接，存储库配置，DNS问题以及所使用的镜像。通过排除并逐个解决这些问题，可以解决"Docker apt-get update"报错的问题。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值