[Question] FATA services.django Additional property platform is not allowed

[scheung38]

Below is example of my production.yml for Django, when

kompose --file production.yml convert

I get:

FATA services.django Additional property platform is not allowed

Why is that please?

.tool-versions python 3.10.4 kompose 1.26.0

---

version: '3'

volumes:
  production_mongodb_data:
  production_traefik: {}

services:
  django:
    build:
      context: .
      dockerfile: ./compose/production/django/Dockerfile
    image: XXXacr.azurecr.io/XXXX_production_django:v1.0.0
    platform: linux/x86_64.      <-----------??????
    depends_on:
      - mongo
    volumes:
      - .:/app:z
      - $HOME/Desktop/XXX_data/_XXX_Data_samples/XXX_MAIN_FILE:/uploaddata  
    
    env_file:
      - ./.envs/.production/.django
      - ./.envs/.production/.mongodb
    ports:
      - "8000:8000"
      - "3000:3000"      
    command: /start
    stdin_open: true
    tty: true

  mongo:
    image: mongo:5.0.6
    container_name: "mongo"
    restart: always
    env_file:
      - ./.envs/.production/.mongodb
    environment:
      - MONGO_INITDB_ROOT_USERNAME=XXXXX
      - MONGO_INITDB_ROOT_PASSWORD=XXXXX
      - MONGO_INITDB_DATABASE= XXXX_mongo 
      - MONGO_INITDB_USERNAME=XXXXX
      - MONGO_INITDB_PASSWORD=XXXXX 
    volumes:
      - production_mongodb_data:/data/db
    ports:
      - 27017:27017

  traefik:
    build:
      context: .
      dockerfile: ./compose/production/traefik/Dockerfile
    image: XXXX_production_traefik
    depends_on:
      - django
    volumes:
      - production_traefik:/etc/traefik/acme:z
    ports:
      - "0.0.0.0:80:80"
      - "0.0.0.0:443:443"

[sergeyshevch]

It's because kompose internally doesn't know how to handle such property as service.platform So you can just remove it from your config if it's not really required or create a PR into kompose with such functional

[scheung38]

So given a docker-compose file we can either create YML manifests out of it and kubectl apply or create helm charts also to do the same thing ?

Sent from my iPhone

On 17 May 2022, at 06:48, Sergey Shevchenko @.***> wrote:

 It's because kompose internally doesn't know how to handle such property as service.platform So you can just remove it from your config if it's not really required or create a PR into kompose with such functional

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.