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

[Feature Request] Runtime secrets #45642

Closed
lonix1 opened this issue May 28, 2023 · 3 comments
Closed

[Feature Request] Runtime secrets #45642

lonix1 opened this issue May 28, 2023 · 3 comments
Labels
kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny

Comments

@lonix1
Copy link

lonix1 commented May 28, 2023

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.

@lonix1 lonix1 added kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny status/0-triage labels May 28, 2023
@neersighted
Copy link
Member

neersighted commented May 30, 2023

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.

@neersighted neersighted closed this as not planned Won't fix, can't repro, duplicate, stale May 30, 2023
@lonix1
Copy link
Author

lonix1 commented May 31, 2023

@neersighted Ok thanks for filing it in the right place.

But please tell me, does that issue cover "runtime secrets" too? (So this feature won't get "lost".)

@lonix1
Copy link
Author

lonix1 commented Jun 5, 2023

@thaJeztah Does that linked issue cover this "runtime secrets" feature request too? So it isn't "forgotten".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny
Projects
None yet
Development

No branches or pull requests

2 participants