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] template_driver being ignored in config #11179
Comments
As noted on https://docs.docker.com/compose/compose-file/compose-file-v3/#configs-configuration-reference:
Docker Compose has no "extensibility" mechanism that would allow to run such a driver (client-side, as compose has no engine component). The closer solution I have in mind for your use-case is compose-spec/compose-spec#429 (not released yet) |
keeping issue opened, as compose should reject a compose file using unsupported attribute |
@ndeloof thank you for both the immediate fix in #11185 and the long-term solution in compose-spec/compose-spec#429 If I want to be informed of when that feature is released, is there an issue/PR/repository/blog I can watch or subscribe to? Or is there a way to test that feature today (using a nightly compose?) |
this will be part of the next docker compose release |
Description
I am trying to use secrets in a config template to work around zitadel not supporting file-based secrets management.
It seems the config is correctly identified and mounted, but not executing the golang template wrapper. I would expect the output to be
Hello, 007
instead ofHello, {{ secret "codename" }}
.Otherwise, I would expect some sort of error message and early exit if
template_driver
is incorrect.compose.yaml
greeting
codename
Steps To Reproduce
Use the above files, then run
docker compose up
, and observe that the configs are not being run through the specified template_driver.Compose Version
Docker Environment
Anything else?
I linked to the wider context/motivation re: zitadel in the original description - if there is a more correct usage of docker features than configs+secrets, I'd love to learn them.
The text was updated successfully, but these errors were encountered: