Yep, but there’s still this: https://github.com/docker/docker/issues/12169
(if we don’t build from source, then there are timing issues around when the tag is created vs when the binaries are available to download from mirrors) Anthony > On Feb 17, 2017, at 2:12 PM, William Markito Oliveira > <william.mark...@gmail.com> wrote: > > What about creating a .dockerignore file ? -> > https://docs.docker.com/engine/reference/builder/#/dockerignore-file > > > > On Fri, Feb 17, 2017 at 10:02 AM, Anthony Baker <aba...@pivotal.io> wrote: > >> >>> On Feb 10, 2017, at 12:29 PM, Anthony Baker <aba...@pivotal.io> wrote: >>> >>> The geode-native build, like most c++ projects, requires a fairly >> specific toolchain. Now that we have a docker build environment [1], I’d >> like to ask INFRA to automate the creation and publishing of docker images >> for geode-native. This can be done by integrating GitHub / DockerHub [2]. >> Note that the docker image would *only* be for build purposes and would not >> contain source or binaries from geode-native. By publishing our build >> toolchain in a docker image: >>> >>> 1) it makes contributing easier >>> 2) it makes our travis-ci builds faster (currently at ~30min) >>> 3) it paves the way to create a nightly Jenkins job for geode-native >>> >>> I suggest publishing this image under the apache namespace [3] as >> geode-native-build. Thoughts? >>> >>> Anthony >>> >>> [1] https://github.com/apache/geode-native/blob/develop/ >> docker/Dockerfile >>> [2] https://issues.apache.org/jira/browse/INFRA-11584?jql= >> project%20%3D%20INFRA%20AND%20text%20~%20docker >>> [3] https://hub.docker.com/u/apache/ >> >> It turns out there are some quirks with automated docker builds. The >> docker container will get rebuilt based on pushes to specific branches or >> when tags are created that match a regex pattern. This is not super useful >> when the container is used to define a build environment. For now, I just >> manually pushed the build image to our docker hub account as: >> >> apachegeode/geode-native-build >> >> We could consider using this automation to build release images. However, >> the Dockerfile must live in the project root and the container size becomes >> larger than just downloading the binaries we publish on ASF. >> >> Anthony >> >> > > > -- > ~/William
