gpt4 book ai didi

docker - Docker镜像有效,Kubernetes Pod不起作用。 Ubuntu的。日志:/bin/sh:[npm,开始]:未找到

转载 作者:行者123 更新时间:2023-12-02 20:55:51 26 4
gpt4 key购买 nike

我正在上一门使用Kubernetes的类(class),尝试在Kubernetes中创建pod时遇到错误。
我正在使用 Ubuntu Ubuntu ,AMD64
我按照以下说明(https://ubuntu.com/kubernetes/install)安装了 microk8s.kubectl
这是我的 Dockerfile ,当我仅使用Docker时,它可以正确运行。

FROM node:alpine

WORKDIR /app

COPY package.json ./
RUN npm install

COPY ./ ./

CMD ["npm", "start"]
这是我的 posts.yaml 文件,与我所修类(class)完全相同
apiVersion: v1
kind: Pod
metadata:
name: posts
spec:
containers:
- name: posts
image: emendoza1986/blog_posts:0.0.1
的输出kubectl获取pod
NAME    READY   STATUS             RESTARTS   AGE
posts 0/1 CrashLoopBackOff 6 10m
的输出kubectl日志发布
/bin/sh: [npm,start]: not found
kubectl的输出描述pod posts
Name:         posts
Namespace: default
Priority: 0
Node: desktope/192.168.0.18
Start Time: Thu, 23 Jul 2020 10:58:40 -0700
Labels: <none>
Annotations: Status: Running
IP: 10.1.87.20
IPs:
IP: 10.1.87.20
Containers:
posts:
Container ID: containerd://acb403c53759670370959cfa2cc0939f53126aee889e1f6dc2e831bc4dc22c3c
Image: emendoza1986/blog_posts:0.0.1
Image ID: docker.io/emendoza1986/blog_posts@sha256:f69b30cf0382d4c273643ac11c505378854b966063974cc57d187718cc0b0fd5
Port: <none>
Host Port: <none>
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 127
Started: Thu, 23 Jul 2020 10:58:59 -0700
Finished: Thu, 23 Jul 2020 10:58:59 -0700
Ready: False
Restart Count: 2
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-2fm2c (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
default-token-2fm2c:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-2fm2c
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 48s default-scheduler Successfully assigned default/posts to desktope
Normal Pulled 29s (x3 over 47s) kubelet, desktope Container image "emendoza1986/blog_posts:0.0.1" already present on machine
Normal Created 29s (x3 over 47s) kubelet, desktope Created container posts
Normal Started 29s (x3 over 47s) kubelet, desktope Started container posts
Warning BackOff 12s (x4 over 45s) kubelet, desktope Back-off restarting failed container
microk8s.status 的输出
microk8s is running
addons:
dashboard: enabled
dns: enabled
metrics-server: enabled
cilium: disabled
fluentd: disabled
gpu: disabled
helm: disabled
helm3: disabled
host-access: disabled
ingress: disabled
istio: disabled
jaeger: disabled
knative: disabled
kubeflow: disabled
linkerd: disabled
metallb: disabled
prometheus: disabled
rbac: disabled
registry: disabled
storage: disabled
的输出microk8s检查
Inspecting Certificates
Inspecting services
Service snap.microk8s.daemon-cluster-agent is running
Service snap.microk8s.daemon-containerd is running
Service snap.microk8s.daemon-apiserver is running
Service snap.microk8s.daemon-apiserver-kicker is running
Service snap.microk8s.daemon-proxy is running
Service snap.microk8s.daemon-kubelet is running
Service snap.microk8s.daemon-scheduler is running
Service snap.microk8s.daemon-controller-manager is running
Service snap.microk8s.daemon-flanneld is running
Service snap.microk8s.daemon-etcd is running
Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system information
Copy processes list to the final report tarball
Copy snap list to the final report tarball
Copy VM name (or none) to the final report tarball
Copy disk usage information to the final report tarball
Copy memory usage information to the final report tarball
Copy server uptime to the final report tarball
Copy current linux distribution to the final report tarball
Copy openSSL information to the final report tarball
Copy network configuration to the final report tarball
Inspecting kubernetes cluster
Inspect kubernetes cluster

Building the report tarball
Report tarball is at /var/snap/microk8s/1503/inspection-report-20200723_112646.tar.gz
我看到错误来自日志,但是我找不到解决方法。谢谢您的帮助!

最佳答案

感谢您的有用评论。最初我有Dockerfile作为
CMD ['npm','start']
我已经在本地修复了
CMD [“npm”,“开始”]
但是我没有将新版本推送到docker hub。
推送新版本可解决此问题。

关于docker - Docker镜像有效,Kubernetes Pod不起作用。 Ubuntu的。日志:/bin/sh:[npm,开始]:未找到,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/63060891/

26 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com