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

More abstract containers #12

Open
tenten8401 opened this issue Jan 22, 2018 · 6 comments
Open

More abstract containers #12

tenten8401 opened this issue Jan 22, 2018 · 6 comments

Comments

@tenten8401
Copy link

tenten8401 commented Jan 22, 2018

Perhaps we could have base images, like base:alpine & base:ubuntu that have the users & directories and whatnot, and then layer gameserver specific changes on top of them, like game:source & game:rust?

@Aaronstar-McClure
Copy link

bump

@parkervcp
Copy link
Member

I don't like the idea of game specific eggs. I get that they need to exist sometimes but I don't think they should.

@parkervcp
Copy link
Member

I do think that we could organize the repo better though on branches.

@parkervcp
Copy link
Member

parkervcp commented Jan 4, 2019

@tenten8401 take a look at https://github.com/parkervcp/images/branches. Is that more like what you are looking for?

@tenten8401
Copy link
Author

@parkervcp the base/ubuntu idea is kinda what I was thinking, but for like ubuntu/wine-source, you could FROM base/ubuntu (or whatever) and then layer wine-source specific changes on top of it, that way you wouldn't have to repeat the user, home, workdir and entrypoint parts of it for every single file.

@parkervcp
Copy link
Member

One issue is that I set the user in the base image and that will interfere with any builds based on those images.

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

3 participants