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

Each user creating its own images that only they can see? #47

Open
nikl11 opened this issue Aug 9, 2021 · 3 comments
Open

Each user creating its own images that only they can see? #47

nikl11 opened this issue Aug 9, 2021 · 3 comments

Comments

@nikl11
Copy link

nikl11 commented Aug 9, 2021

Hello, I wanted to use this tljh with repo2docker plugin (as a replacement for binderhub which I have trouble setting up) for our independent users. I would like it to work like this: our users login to different servers via kerberos authentication, so I would like them to be able to login, create their own environment, and run them, without any other user being able to access an image of another user. I thought this is how this plugin works by default, but I see only admins can access Environments, and the every created image is visible to all users. Is there any way to do it the my way, each user has its own images that they can build or run? Thanks.

@adriendelsalle
Copy link

Hey @nikl11

If I understand well your use case, you would prefer that any user could trigger an image build.
This sounds like a small modification to have it configurable if not yet possible.
Just keep in mind administration of the server: you could pretty quickly fill your filesystem with plenty images and I'm not sure there is a way to set an upper limit and a culling strategy on images.

@nikl11
Copy link
Author

nikl11 commented Sep 2, 2021

Thank you @adriendelsalle , yes it is probably easy to configure for the person who created this plugin, but for me with my current "scope" of options available, I can allow other users to build only by making them admins (which lets face it is not a solution as admins can sabotage everything if they dont what what they are doing). But that is not the main issue, the main issue for me is to have users and their images that they have built linked together and separated (in other words if user A creates images X and Y, user B creates Z, user C creates nothing, then A sees only X and Y, B sees only Z and C sees nothing. I kinda has an idea that I could prepend every image name with the users name, so like my-test-image.img would become username-my-test-image.img and then filter all the available images for the current using like "docker images | grep username ...", but again no idea where and how to implement that.

@adriendelsalle
Copy link

Your main issue looks effectively more complicated than making all users capable of building images.
I'll try to give you some pointers if I have time soon-ish.

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

2 participants