shahidhk / go-docker

Sample code and dockerfiles accompanying the blog post The Ultimate Guide to Writing Dockerfiles for Go Web-apps

go-docker

A simple web app written in Go, with dockerfiles for development and production.

Build and run using any dockerfile:

$ docker build -f [dockerfile] -t go-docker .
$ docker run --rm -it -p 8080:8080 go-docker

See branch glide for glide based workflow instead of dep.

go-docker's Issues

bad url in the github header

The link to the blog post is broken.

The good link is https://blog.hasura.io/the-ultimate-guide-to-writing-dockerfiles-for-go-web-apps-336efad7012c/.

使用1-simple.dockerfile ，创建镜像，运行镜像时，找不到jar

1负责文件
2[root@localhost go-docker]# docker build -t go-docker-dev .
Sending build context to Docker daemon 2.731 MB
Step 1/4 : FROM golang:1.8.5-jessie
---> ba52c9ef0f5c
Step 2/4 : WORKDIR /go/src/app
---> effc79fb9241
Removing intermediate container 15b6cd759a61
Step 3/4 : ADD src src
---> ca68dbcf11e8
Removing intermediate container 440c214ff105
Step 4/4 : CMD go run src/main.go
---> Running in 29ac9d1444eb
---> 95251f8b50f2
Removing intermediate container 29ac9d1444eb
Successfully built 95251f8b50f2
[root@localhost go-docker]# docker run --rm -it -p 8090:8080 go-docker-dev
src/main.go:8:2: cannot find package "github.com/sirupsen/logrus" in any of:
/usr/local/go/src/github.com/sirupsen/logrus (from $GOROOT)
/go/src/github.com/sirupsen/logrus (from $GOPATH)
[root@localhost go-docker]#
3、报错。

What do you do when your project depends on your own source code?

This file ALMOST takes me there:

• https://github.com/shahidhk/go-docker/blob/master/5-multi-stage-prod.dockerfile

But if src/main.go is instead cmd/main.go:

import "github.com/shahidhk/go-docker/pkg/printfoo"
func main() {
  printfoo.Print()
}

And the contents of pkg/printfoo.go are:

package printfoo
func Print() {
  fmt.Println("foo")
}

Then dep will pull into Gopkg.toml whatever is checked in to GitHub with --vendor-only for pkg/printfoo and not what is local. Especially if this Dockerfile lives in cmd/ which is what you would want to do if you were making a number of different binaries for command line programs but that all use a common library.

What do you do in these cases other than continuously checking your code into GitHub to ensure the dependency pulls the latest stuff from pkg/...? The Dockerfile is not permitted to do a COPY ../pkg ./ so I am not sure how to do this without placing the Dockerfile in the root of the project. Thank you for your help in advance!