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
>
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 wrote:
>
> > On Feb 10, 2017, at 12:29 PM, Anthony Baker wrote:
> >
> > The geode-native build, like most c++ projects, requires
> On Feb 10, 2017, at 12:29 PM, Anthony Baker 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-nativ
+1
On Fri, Feb 10, 2017 at 1:14 PM, Michael William Dodge
wrote:
> I think this would be a good idea as configuring a machine for building
> can be a barrier to entry for people wishing to contribute.
>
> Sarge
>
> > On 10 Feb, 2017, at 12:29, Anthony Baker wrote:
> >
> > The geode-native build
I think this would be a good idea as configuring a machine for building can be
a barrier to entry for people wishing to contribute.
Sarge
> On 10 Feb, 2017, at 12:29, Anthony Baker wrote:
>
> The geode-native build, like most c++ projects, requires a fairly specific
> toolchain. Now that we
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
