Question

我准备好了docker-compose设置的项目。现在我想搬到kubernetes。我使用Kompose工具将docker-compose转换为kubernetes。

例如，这是我的样本docker-compose.yml文件

version: '3'
volumes:
  database_hades_volume:
    external: true
services:
  db:
    image: postgres:latest
    container_name: hades-db
    ports:
      - "5432:5432"
    environment:
      POSTGRES_DB: hades_dev
      POSTGRES_PASSWORD: 1234
    volumes:
    - database_hades_volume:/var/lib/postgresql/data/
    tty: true
    stdin_open: true
  redis:
    container_name: hades-redis
    image: redis:latest
    ports:
      - "6379:6379"
  app:
    container_name: hades-app
    build:
      context: .
      dockerfile: Dockerfile
    ports:
      - "4001:4001"
    volumes:
      - ".:/webapp"
    env_file:
      - ./.env.docker_compose-dev
    depends_on:
      - db
      - redis

我使用命令docker-compose up成功运行。现在，我使用kompose使用命令转换为kubernetes：

kompose convert

然后我继续使用：

kompose up

这是命令行结果信息：

INFO We are going to create Kubernetes Deployments, Services and PersistentVolumeClaims for your Dockerized application. If you need different kind of resources, use the 'kompose convert' and 'kubectl create -f' commands instead.

INFO Deploying application in "default" namespace
INFO Successfully created Service: app
INFO Successfully created Service: db
INFO Successfully created Service: redis
INFO Successfully created Deployment: app
INFO Successfully created PersistentVolumeClaim: app-claim0 of size 100Mi. If your cluster has dynamic storage provisioning, you don't have to do anything. Otherwise you have to create PersistentVolume to make PVC work
INFO Successfully created Deployment: db
INFO Successfully created PersistentVolumeClaim: database-hades-volume of size 100Mi. If your cluster has dynamic storage provisioning, you don't have to do anything. Otherwise you have to create PersistentVolume to make PVC work
INFO Successfully created Deployment: redis

Your application has been deployed to Kubernetes. You can run 'kubectl get deployment,svc,pods,pvc' for details.

但是当我尝试前往localhost:4001或10.0.0.180:4001进行测试时，我发现它正在等待。

我不知道我是否设置错误或错过了一些步骤。请帮帮我。

由于

Answer 1

你的docker-compose文件包含build键，这意味着你有app服务的源代码/ Dockerfile，截至目前，

NAME READY STATUS RESTARTS AGE po/app-2119952459-b4jtb 0/1 ErrImagePull 0 24s

状态为ErrImagePull，因为群集无法找到任何图片，因此与build密钥一起提供image密钥，对于前 app: container_name: hades-app build: context: . dockerfile: Dockerfile image: <username>/<imagename>:<tag>

因为，现在kompose具有本地构建和推送支持的功能，因此，kompose将构建您的图像，推送到dockerhub，然后您的群集可以在部署时从那里提取图像。

命令可以是，

kompose up --build=local

我希望这是有道理的

无法使用kompose从docker-compose转换为kubernetes

1 个答案: