diff --git a/Dockerfile-deb b/Dockerfile-deb
index 62556ac..53d75d8 100644
--- a/Dockerfile-deb
+++ b/Dockerfile-deb
@@ -12,10 +12,11 @@ ADD . /opt/go/src/github.com/QubitProducts/bamboo
 WORKDIR /opt/go/src/github.com/QubitProducts/bamboo
 
 RUN go get github.com/tools/godep && \
-    go get -t github.com/smartystreets/goconvey
+    go get -t github.com/smartystreets/goconvey && \
+    go build
 
 RUN mkdir -p /output
 VOLUME /output
 
 ENV USER root
-CMD builder/build.sh && mv builder/bamboo*.deb /output
+CMD builder/build.sh && mv output/bamboo*.deb /output
diff --git a/README.md b/README.md
index b4c0348..5d20738 100644
--- a/README.md
+++ b/README.md
@@ -237,10 +237,10 @@ Moreover, there is
 - a [Jenkins build script](builder/ci-jenkins.sh) to run `build.sh` from a Jenkins job
 - and a [Docker build container](builder/build.sh) which will generate the deb package in the volume mounted output directory:
 
-  ```
-  docker build -f Dockerfile-deb -t bamboo-build
-  docker run -it -v $(pwd)/output bamboo-build
-  ```
+```
+docker build -f Dockerfile-deb -t bamboo-build .
+docker run -it -v $(pwd)/output:/output bamboo-build
+```
 
 Independently how you build the deb package, you can copy it to a server or publish to your own apt repository.