-
Notifications
You must be signed in to change notification settings - Fork 1
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
USM-20-update-docker #21
base: master
Are you sure you want to change the base?
USM-20-update-docker #21
Conversation
Codecov Report
@@ Coverage Diff @@
## master #21 +/- ##
=======================================
Coverage 77.27% 77.27%
=======================================
Files 4 4
Lines 66 66
=======================================
Hits 51 51
Misses 13 13
Partials 2 2 Continue to review full report at Codecov.
|
@@ -2,4 +2,4 @@ FROM docker.io/microlib/golang-base:1.7 | |||
|
|||
# This will change depending on each microservice entry point | |||
# This will change to the binary start in production based images | |||
CMD ["/bin/sh", "go run main.go"] | |||
CMD ["/usr/local/go/bin/go", "run", "main.go"] |
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.
@luigizuccarelli I was wondering if we shouldn't add an ENTRYPOINT
that simply runs the go
executable. And then the CMD
on top of that. In that way we might not need to change the Dockerfile for production, we just run it with a different command.
What do you think?
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.
Yes entrypoint is the correct way
Title:
Updated Dockerfile to allow for simple entry point start for local dev and updated the README
Motivation:
Allow the local developer to build and execute docker container locally
Resolution:
Added simple instructions in the README
Ticket:
USM-20