Re-build Go (App Engine) app running inside docker container?

Normally, when you run a Go app using Go-Appengine’s goapp serve command, file changes are detected and initiate a re-build.

INFO     2015-01-11 ... Detected file changes: ...

I’m currently experimenting with running Go-Appengine inside a docker container, and while the server starts appropriately, file changes do not initiate a re-build. How do I make this happen?

  • Networking in Docker Swarm, and why we need a proxy
  • docker image - centos 7 > ssh service not found
  • Go Web app on AWS with Elastic Beanstalk not showing output in logs
  • Docker Couchbase Failed to connect to 127.0.0.1 port 8091: Connection refused
  • Docker SCRATCH container can't find files
  • Can't push or pull to/from docker registry on localhost
  • From my personal experience, Django projects running inside and outside docker containers behave the same way when file changes are detected.

  • Memory issues when running Keras inside Docker on a Mac
  • Dockerfile build error on RUN npm install
  • cant connect to docker daemon - eclipse che
  • How to take Oracle-xe-11g backup from running Docker container
  • How do I set environment variables during the build in docker
  • Moving Docker Containers Around
  • One Solution collect form web for “Re-build Go (App Engine) app running inside docker container?”

    I think the problem here is that the files don’t change inside the docker-container, only on the host-filesystem. Your source-directory is added in the Dockerfile (when the container-image is built). If you change the files later, the container is not automatically rebuilt.

    To solve this issue (for development-purposes) you could mount the source-directory from your host-system into the docker-container. with this trick, source-changes are automatically added to the container.

    To to this, add

    volumes:
      - .:/go/src
    
    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.