无法在Openshift上部署cloudera manager映像

无法在Openshift上部署cloudera manager映像,openshift,cloudera-manager,Openshift,Cloudera Manager,对不起,我不知道这是否是发布此消息的正确位置 我正在尝试使用cloudera manager来实现一个简单的spark应用程序 但我就是不能,我尝试部署到docker hub的每个映像都失败了(我可以部署其他映像,但cloudera manager的映像不行) 如果你有什么建议,我将不胜感激 谢谢 编辑1: [openshift@acs-test-master-0 ~]$ oc new-app cloudera/quickstart --> Found Docker ima

对不起,我不知道这是否是发布此消息的正确位置

我正在尝试使用cloudera manager来实现一个简单的spark应用程序

但我就是不能,我尝试部署到docker hub的每个映像都失败了(我可以部署其他映像,但cloudera manager的映像不行)

如果你有什么建议,我将不胜感激

谢谢

编辑1:

    [openshift@acs-test-master-0 ~]$ oc new-app cloudera/quickstart
    --> Found Docker image 2cda829 (14 months old) from Docker Hub for "cloudera/quickstart"

        * An image stream will be created as "quickstart:latest" that will track this image
        * This image will be deployed in deployment config "quickstart"
        * The image does not expose any ports - if you want to load balance or send traffic to this component
          you will need to create a service with 'expose dc/quickstart --port=[port]' later
        * WARNING: Image "cloudera/quickstart" runs as the 'root' user which may not be permitted by your cluster administrator

    --> Creating resources ...
        imagestream "quickstart" created
        deploymentconfig "quickstart" created
    --> Success
        Run 'oc status' to view your app.

    [openshift@acs-test-master-0 ~]$ oc status
    In project hkouki on server https://10.64.178.245:8443

    dc/quickstart deploys istag/quickstart:latest
      deployment #1 running for 9 seconds - 1 pod

    3 warnings identified, use 'oc status -v' to see details.
    [openshift@acs-test-master-0 ~]$ oc status -v
    In project hkouki on server https://10.64.178.245:8443

    dc/quickstart deploys istag/quickstart:latest
      deployment #1 running for 17 seconds - 1 pod

    Warnings:
      * pod/quickstart-1-deploy has no liveness probe to verify pods are still running.
        try: oc set probe pod/quickstart-1-deploy --liveness ...
      * dc/quickstart has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
        try: oc set probe dc/quickstart --readiness ...
      * dc/quickstart has no liveness probe to verify pods are still running.
        try: oc set probe dc/quickstart --liveness ...

    View details with 'oc describe <resource>/<name>' or list everything with 'oc get all'.

[openshift@acs-test-master-0 ~]$ oc get events
LASTSEEN   FIRSTSEEN   COUNT     NAME                  KIND      SUBOBJECT                     TYPE      REASON       SOURCE                    MESSAGE
11m        11m         1         quickstart-1-deploy   Pod                                     Normal    Scheduled    {default-scheduler }      Successfully assigned quickstart-1-deploy to 192.168.232.2
11m        11m         1         quickstart-1-deploy   Pod       spec.containers{deployment}   Normal    Pulled       {kubelet 192.168.232.2}   Container image "openshift3/ose-deployer:v3.4.0.39" already present on machine
11m        11m         1         quickstart-1-deploy   Pod       spec.containers{deployment}   Normal    Created      {kubelet 192.168.232.2}   Created container with docker id b68834b1d135; Security:[seccomp=unconfined]
11m        11m         1         quickstart-1-deploy   Pod       spec.containers{deployment}   Normal    Started      {kubelet 192.168.232.2}   Started container with docker id b68834b1d135
1m         1m          1         quickstart-1-deploy   Pod       spec.containers{deployment}   Normal    Killing      {kubelet 192.168.232.2}   Killing container with docker id b68834b1d135: Need to kill pod.
11m        11m         1         quickstart-1-pbbtt    Pod                                     Normal    Scheduled    {default-scheduler }      Successfully assigned quickstart-1-pbbtt to 192.168.232.2
1m         11m         34        quickstart-1-pbbtt    Pod       spec.containers{quickstart}   Normal    Pulling      {kubelet 192.168.232.2}   pulling image "cloudera/quickstart@sha256:f91bee4cdfa2c92ea3652929a22f729d4d13fc838b00f120e630f91c941acb63"
1m         11m         34        quickstart-1-pbbtt    Pod       spec.containers{quickstart}   Normal    Pulled       {kubelet 192.168.232.2}   Successfully pulled image "cloudera/quickstart@sha256:f91bee4cdfa2c92ea3652929a22f729d4d13fc838b00f120e630f91c941acb63"
1m         11m         34        quickstart-1-pbbtt    Pod       spec.containers{quickstart}   Warning   Failed       {kubelet 192.168.232.2}   Failed to create docker container "quickstart" of pod "quickstart-1-pbbtt_hkouki(ead5ca64-4ce6-11e7-9cd6-fa163ec8e6c3)" with error: Error response from daemon: {"message":"No command specified"}
    1m         11m         34        quickstart-1-pbbtt    Pod                                     Warning   FailedSync   {kubelet 192.168.232.2}   Error syncing pod, skipping: failed to "StartContainer" for "quickstart" with RunContainerError: "runContainer: Error response from daemon: {\"message\":\"No command specified\"}"

    11m       11m       1         quickstart-1   ReplicationController             Normal    SuccessfulCreate              {replication-controller }        Created pod: quickstart-1-pbbtt
    1m        1m        1         quickstart-1   ReplicationController             Normal    SuccessfulDelete              {replication-controller }        Deleted pod: quickstart-1-pbbtt
    11m       11m       1         quickstart     DeploymentConfig                  Normal    DeploymentCreated             {deploymentconfig-controller }   Created new replication controller "quickstart-1" for version 1
    1m        1m        1         quickstart     DeploymentConfig                  Normal    ReplicationControllerScaled   {deploymentconfig-controller }   Scaled replication controller "quickstart-1" from 1 to 0
    [openshift@acs-test-master-0 ~]$ oc get all
    NAME            DOCKER REPO                             TAGS      UPDATED
    is/quickstart   172.30.228.225:5000/hkouki/quickstart   latest    7 minutes ago

    NAME            REVISION   DESIRED   CURRENT   TRIGGERED BY
    dc/quickstart   1          1         1         config,image(quickstart:latest)

    NAME              DESIRED   CURRENT   READY     AGE
    rc/quickstart-1   1         1         0         7m

    NAME                     READY     STATUS              RESTARTS   AGE
    po/quickstart-1-deploy   1/1       Running             0          7m
    po/quickstart-1-pbbtt    0/1       RunContainerError   0          7m
[openshift@acs-test-master-0~]$oc新应用cloudera/quickstart
-->从Docker Hub中找到“cloudera/quickstart”的Docker图像2cda829(14个月前)
*将创建一个图像流作为“quickstart:latest”,用于跟踪此图像
*此映像将部署在部署配置“quickstart”中
*如果您希望负载平衡或向此组件发送流量,则映像不会公开任何端口
稍后您将需要使用“expose dc/quickstart--port=[port]”创建一个服务
*警告:映像“cloudera/quickstart”以“root”用户身份运行,这可能是群集管理员不允许的
-->正在创建资源。。。
已创建imagestream“快速启动”
已创建deploymentconfig“快速启动”
-->成功
运行“oc状态”查看您的应用程序。
[openshift@acs-test-master-0~]$oc状态
在服务器上的hkouki项目中https://10.64.178.245:8443
dc/quickstart部署istag/quickstart:最新版本
部署#1运行9秒-1个吊舱
已识别3个警告,请使用“oc状态-v”查看详细信息。
[openshift@acs-test-master-0~]$oc状态-v
在服务器上的hkouki项目中https://10.64.178.245:8443
dc/quickstart部署istag/quickstart:最新版本
部署#1运行17秒-1个吊舱
警告:
*pod/quickstart-1-deploy没有活动探测器来验证pod是否仍在运行。
try:oc设置探测吊舱/quickstart-1-deploy——活跃度。。。
*dc/quickstart没有准备就绪探测器来验证POD是否准备好接受流量或确保部署成功。
try:oc set probe dc/quickstart--准备就绪。。。
*dc/quickstart没有活动探测器来验证POD是否仍在运行。
try:oc-set-probe-dc/quickstart-liveness。。。
使用“oc descripe/”查看详细信息,或使用“oc get all”列出所有内容。
[openshift@acs-test-master-0~]$oc get事件
LASTSEEN FIRSTSEEN计数名称种类子对象类型原因源消息
11m 11m 1 quickstart-1-deploy Pod正常调度{default scheduler}已成功将quickstart-1-deploy分配给192.168.232.2
11m 11m 1 quickstart-1-deploy Pod spec.containers{deployment}正常拉取{kubelet 192.168.232.2}容器映像“openshift3/ose部署器:v3.4.0.39”已存在于计算机上
11m 11m 1 quickstart-1-deploy Pod spec.containers{deployment}正常创建的{kubelet 192.168.232.2}使用docker id b68834b1d135创建的容器;安全:[seccomp=unconfined]
11m 11m 1 quickstart-1-deploy Pod spec.containers{deployment}正常启动{kubelet 192.168.232.2}已启动docker id为b68834b1d135的容器
1m 1m 1 quickstart-1-deploy Pod spec.containers{deployment}正常终止{kubelet 192.168.232.2}终止docker id为b68834b1d135的容器:需要终止Pod。
11m 11m 1 quickstart-1-pbbtt Pod正常调度{默认调度程序}已成功将quickstart-1-pbbtt分配给192.168.232.2
1m 11m 34 quickstart-1-pbbtt吊舱规格容器{quickstart}正常拉动{kubelet 192.168.232.2}拉动图像“cloudera”/quickstart@sha256:F91BEE4CDFA2C92EA3652929A22F729D4D13FC838B0F120E630F91C941ACB63“
1m 11m 34 quickstart-1-pbbtt吊舱规格容器{quickstart}正常拉取{kubelet 192.168.232.2}成功拉取图像“cloudera”/quickstart@sha256:F91BEE4CDFA2C92EA3652929A22F729D4D13FC838B0F120E630F91C941ACB63“
1m 11m 34 quickstart-1-pbbtt Pod spec.containers{quickstart}警告失败{kubelet 192.168.232.2}无法创建Pod“quickstart-1-pbbtt_hkouki(ead5ca64-4ce6-11e7-9cd6-fa163ec8e6c3)”的docker容器“quickstart”,错误:守护程序的错误响应:{“消息”:“未指定命令”}
1m 11m 34 quickstart-1-pbbtt Pod警告失败同步{kubelet 192.168.232.2}错误同步Pod,跳过:无法使用runContainer启动“quickstart”的“StartContainer”错误:“runContainer:来自守护程序的错误响应:{\”消息\“:\”未指定命令\}”
11m 11m 1 quickstart-1复制控制器正常成功创建{replication controller}已创建pod:quickstart-1-pbbtt
1m 1m 1 quickstart-1复制控制器正常成功删除{replication controller}已删除pod:quickstart-1-pbbtt
11m 11m 1 quickstart DeploymentConfig普通部署已创建{DeploymentConfig controller}已为版本1创建新的复制控制器“quickstart-1”
1m 1m 1 quickstart DeploymentConfig普通复制控制器缩放{DeploymentConfig controller}将复制控制器“quickstart-1”从1缩放到0
[openshift@acs-test-master-0~]$oc获取全部
更新DOCKER REPO标记的名称
is/quickstart 172.30.228.225:5000/hkouki/quickstart最近7分钟前发布
名称修订所需电流已触发