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

user credentials #201

Closed
cgwalters opened this issue Feb 14, 2024 · 2 comments
Closed

user credentials #201

cgwalters opened this issue Feb 14, 2024 · 2 comments

Comments

@cgwalters
Copy link
Contributor

We had a realtime chat on what specifically we should support configuring when generating disk images (as opposed to injecting into the container image). @mvo5 mentioned that the test suite right now relies on injecting a root ssh key. Yes, but note that it's also possible to inject a key in two other ways:

That said, note that containers/bootc@e477e4f also landed, so I think it would clearly make sense to expose that too, particularly after #18 is done.

There is still a much thornier question of the general problem of secrets, to which it's hard to have one opinionated answer (this touches on containers/bootc#22 etc.)

@cgwalters
Copy link
Contributor Author

As a derived container image

Also I did #135 earlier related to this...I think it's definitely good for bib to test the generic base image, but arguably the first and most important test is (one or more) derived images, with the base image more as a special case.

@cgwalters
Copy link
Contributor Author

Eh, this one isn't actionable; closing in favor of #143

@cgwalters cgwalters closed this as not planned Won't fix, can't repro, duplicate, stale Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant