GCR Builds fail

In the last week all of my builds with Google Cloud Registry fail with the following message after 1 minute of build time:

Error response from daemon: No such container: b673590505f0d07c58c5d6413d46d522b4f17549ebe72c523230eff0f8772e6f

  • datadog agent not reachable from inside docker container
  • Issues on Apache when sharing files in between docker and Mac OS X
  • Docker Couchbase: Cannot connect to port 8091 using curl from within entrypoint script
  • how to access docker registry v2 with curl?
  • Rsync (or ssh) to a remote docker container on EC2
  • HTTP/2 nginx force redirect HTTP to HTTPS breaks expected behaviour
  • Error: No such container: b673590505f0d07c58c5d6413d46d522b4f17549ebe72c523230eff0f8772e6f

    seem like the build containers are dying?

  • What is the difference between CMD and ENTRYPOINT in a Dockerfile?
  • docker-compose: accessing postgres' shell (psql)
  • How to make Hazelcast nodes installed in docker on different aws instances interact with each other?
  • Virtualbox inside docker container without host dependency
  • How to install multiple packages using apt-get via a Dockerfile
  • How to link two docker services in coreos with flannel?
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.