-
Notifications
You must be signed in to change notification settings - Fork 59
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
merge of fedora-toolbox and coreos-toolbox efforts #90
Comments
In the weekly meeting today we discussed merging the
|
For the record, what are the practical differences between the two modes? |
Hm, I think of the "debugging, privileged" case as "general sysadmin work". For example, running |
@dustymabe I think we can close this, right? FCOS now ships toolbox. Re. specifically about the running as root case, if it's indeed the case that it doesn't work yet (as per containers/toolbox#267), we should open a new ticket and bump priority on that. |
From @debarshiray:
Goal:
Evaluate the current state of fedora-toolbox on Fedora CoreOS; identify
problems and use-cases; and start filing issues and writing patches.
Background:
So far, fedora-toolbox has been written, tested and used solely on Fedora
Silverblue systems. In short (here is a longer write-up), on Silverblue,
fedora-toolbox is meant to offer a mutable RPM-based development environment
that's seamlessly integrated with the host OS. That means running rootless,
shared $HOME, access to hardware like GPUs, etc.. It's not about security,
but giving the developer a safe sandbox to tinker in without breaking the host
OS or being conscious of the underlying container technology.
From @dustymabe:
The above writeup is from @debarshiray. There seems to be some general agreement that we'd like to merge the efforts of https://github.com/debarshiray/fedora-toolbox and https://github.com/coreos/toolbox. Let's discuss at our next meeting how we can get there.
Previous discussions:
The text was updated successfully, but these errors were encountered: