-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add Dockerfile #1
base: master
Are you sure you want to change the base?
Conversation
|
||
RUN gem install --no-document etcenv | ||
|
||
RUN groupadd -g 500 core && useradd -u 500 -g 500 core |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CoreOS specific stuff?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, right, had a specific use case for that. But that's not even the case anymore. I'll remove that commit.
Sorry for late reply! |
@@ -0,0 +1,5 @@ | |||
FROM ruby | |||
|
|||
RUN gem install --no-document etcenv |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RUN mkdir /app
WORKDIR /app
ADD . /app
RUN bundle install
ENTRYPOINT ["bundle", "exec", "etcenv"]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, building from source is even better ;)
But bundler is not needed here. I changed it to use the normal gem build procedure now. Just take whichever you like best..
Also, please consider adding an automated build to the Docker registry hub afterwards. This makes it easier to run e.g. on CoreOS.
Thanks for your work!