Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] mapping format of services[].env_file is not supported #1855

Closed
jancespivo opened this issue Apr 16, 2024 · 2 comments
Closed

[BUG] mapping format of services[].env_file is not supported #1855

jancespivo opened this issue Apr 16, 2024 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@jancespivo
Copy link

jancespivo commented Apr 16, 2024

Expected Behavior

Mapping format as it is described https://docs.docker.com/compose/compose-file/05-services/#env_file should be supported.

env_file:
  - path: ./default.env
    required: true # default
  - path: ./override.env
    required: false

Actual Behavior

FATA Unable to load files: validating [REDACTED]/docker-compose.yml: services.kuard.env_file.0 must be a string

Steps To Reproduce

No response

Kompose Version

1.32.0 (765fde254)

Docker-Compose file

services:
  kuard:
    image: gcr.io/kuar-demo/kuard-amd64:blue
    env_file:
      - path: ./default.env
        required: true # default
      - path: ./override.env
        required: false
    ports:
      - target: 8080
        published: 8080

Anything else?

No response

@jancespivo jancespivo added the kind/bug Categorizes issue or PR as related to a bug. label Apr 16, 2024
@sosan
Copy link
Contributor

sosan commented Apr 17, 2024

related to pr #1838

@k8s-triage-robot
Copy link

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

This bot triages un-triaged 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:

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

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants