Katenary/katenary
2
0
Fork 3
Code Issues 13 Pull Requests 2 Actions Packages Projects 4 Releases 18 Wiki Activity

Docker compose >=2.24.0 env_file syntax #102

New Issue
Closed
opened 2024-12-21 09:54:28 +00:00 by GSergeevich · 3 comments
GSergeevich commented 2024-12-21 09:54:28 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Hi!

The docker compose since version 2.24.0 has a new syntax

As of Docker Compose version 2.24.0, you can set your .env file, defined by the env_file attribute, to be optional by using the required field. When required is set to false and the .env file is missing, Compose silently ignores the entry.

env_file:

  • path: ./default.env
    required: true # default
  • path: ./override.env
    required: false

so

katenary convert docker-compose.yml
validating docker-compose.yml: services.portal.env_file.0 must be a string
Hi! The docker compose since version 2.24.0 has a [new syntax](https://docs.docker.com/compose/how-tos/environment-variables/set-environment-variables/#additional-information-1) > As of Docker Compose version 2.24.0, you can set your .env file, defined by the env_file attribute, to be optional by using the required field. When required is set to false and the .env file is missing, Compose silently ignores the entry. > > env_file: > - path: ./default.env > required: true # default > - path: ./override.env > required: false so ``` katenary convert docker-compose.yml validating docker-compose.yml: services.portal.env_file.0 must be a string ```
GSergeevich commented 2024-12-21 10:35:14 +00:00 (Migrated from github.com)
Copy Link
Copy Source

As I discovered, support for the new syntax was added to the compose-go library in release 2.0.0:
https://github.com/compose-spec/compose-go/releases/tag/v2.0.0

As I discovered, support for the new syntax was added to the compose-go library in release 2.0.0: https://github.com/compose-spec/compose-go/releases/tag/v2.0.0
metal3d commented 2024-12-28 14:26:24 +00:00
Copy Link
Copy Source

Thanks for your report.

I will need to update the compose-go package, which isn't compatible with the previous package. And the entire Katenary codebase uses the definition.

I will try to use the v2 in a few days.

Thanks for your report. I will need to update the compose-go package, which isn't compatible with the previous package. And the entire Katenary codebase uses the definition. I will try to use the v2 in a few days.
👍 1
metal3d added this to the Use compose v2 project 2025-09-14 12:20:44 +00:00
metal3d moved this to In Progress in Use compose v2 on 2025-10-18 13:34:02 +00:00
metal3d commented 2025-10-18 13:35:02 +00:00
Copy Link
Copy Source

commit 569ca195df fixes this

commit 569ca195dfcc201f29de802be8e46789c8d6a5c2 fixes this
metal3d moved this to Done in Use compose v2 on 2025-10-18 13:35:13 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 dependencies
Pull requests that update a dependency file
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 go
Pull requests that update go code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 partially fixed
Some fixes are already made in current release / developpement
 question
Further information is requested
 wontfix
This will not be worked on
No labels enhancement
Milestone
No items
No Milestone v3.0.1
Projects
Clear projects
No projects
Use compose v2
Done
Assignees
Clear assignees
metal3d (Patrice Ferlet)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Katenary/katenary#102