Nicolas De loof
Nicolas De loof
Did you maybe used a public AMI I could use to try replicate this issue ?
let's close this issue. If anyone comes into the same issue, feel free to comment or open a follow-up issue
> is docker stack config using docker compose v2 under the hood Nope, `docker stack` still relies on legacy docker/cli codebase to parse compose.yaml and didn't adopted the compose-specification (see...
re-opening issue as this also applies to compose v2
The root cause here is that compose-go maps compose.yaml to go structs, with typed attributes. So it _needs_ to convert input into `int` and can't manage a yaml input with...
compose-go/v2 is currently in development and will allow to process compose files as plain yaml trees, without relying on typed go structs. This will allow to validate a compose file...
While compose-go/v2 is a first place toward a parser which can process `compose.yaml` with non-interpolated values, this is not ready yet so it can fully implement `docker compose config` feature....
tested with latest v2.17.3 release, and get the expected variable set: ``` TO_REFERENCE=world! WORKING_SUBSTITUTION=Hello world! NON_WORKING_SUBSTITUTION=Hello beautiful world! ``` so, closing this issue as fixed. Feel free to comment or...
docker compose v2 indeed does: - parse a yaml file into a tree - interpolate variables - map tree to internal model based on go structs - merge with any...
@storm1er you could declare variable with a default value, so you don't even need an override file in development: ```yaml services: web: image: registry.gitlab.com///:${TAG:-dev} ```