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

Support for content in top-level config #1947

Open
jvitor83 opened this issue Oct 29, 2024 · 0 comments · May be fixed by #1952
Open

Support for content in top-level config #1947

jvitor83 opened this issue Oct 29, 2024 · 0 comments · May be fixed by #1952
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@jvitor83
Copy link
Contributor

What would you like to be added?

Support for content in the top-level config as it states in https://docs.docker.com/reference/compose-file/configs/ released in Docker Compose version 2.23.1

services:

  hello:
    image: nginxdemos/hello
    configs:
      - source: conf-name
        target: /etc/dynamic.yaml

configs:
  conf-name:
    content: |
      some-setting: true

Currently it gives:
FATA Unable to retrieve file: Unable to read file: open : The system cannot find the file specified.

Why is this needed?

To keep the compatibility synced between docker-compose and kompose.

@jvitor83 jvitor83 added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 29, 2024
@jvitor83 jvitor83 changed the title Support for content in top-level config Support for content in top-level config Oct 29, 2024
jvitor83 added a commit to jvitor83/kompose that referenced this issue Nov 6, 2024
@jvitor83 jvitor83 linked a pull request Nov 6, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant