You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There have been requests for runtime (/mounted) secrets going back years. (I'm not referring to build-time secrets.) Unfortunately this is not currently supported.
Here's a question on StackOverflow with 10k views so far. There was a PR for this feature, but was abandoned.
The typical workaround is to create a one-node swarm. Although that works, it's a pain to set up and maintain just to get the secrets feature. Also, it's not possible to do that with docker rootless as the overlay network doesn't work, so swarm isn't available.
Now that docker compose is integrated into the core cli tool, please consider adding this feature. It's something people have asked for going back many years because it's not just useful, but incredibly important: a core part of a deployment's security.
The text was updated successfully, but these errors were encountered:
This is a duplicate, more-or-less of #13490. While #13490 is less concrete, it's still the best place to start thinking about how secrets should be implemented in the future.
I'll make a note to link back here when we come up with a basic design proposal/set of principles and a better tracking issue in the feature.
Description
There have been requests for runtime (/mounted) secrets going back years. (I'm not referring to build-time secrets.) Unfortunately this is not currently supported.
Here's a question on StackOverflow with 10k views so far. There was a PR for this feature, but was abandoned.
The typical workaround is to create a one-node swarm. Although that works, it's a pain to set up and maintain just to get the secrets feature. Also, it's not possible to do that with docker rootless as the overlay network doesn't work, so swarm isn't available.
Now that
docker compose
is integrated into the core cli tool, please consider adding this feature. It's something people have asked for going back many years because it's not just useful, but incredibly important: a core part of a deployment's security.The text was updated successfully, but these errors were encountered: