Hi friends,
A ruby-based build task has begun failing at the ‘Spin Up Environment’ step. It seems to correlate with some rolling updates to the docker images occurring right now. This is the output of the step:
Build-agent version 0.1.1073-1f69f340 (2018-11-20T18:07:03+0000)
Starting container circleci/ruby:2.5-node
image cache not found on this host, downloading circleci/ruby:2.5-node
2.5-node: Pulling from circleci/ruby
54f7e8ac135a: Already exists
d6341e30912f: Already exists
087a57faf949: Already exists
5d71636fb824: Already exists
0c1db9598990: Already exists
341f09e17d45: Pulling fs layer
569a895c540d: Pulling fs layer
8167a8de89c3: Pulling fs layer
341f09e17d45: Download complete
341f09e17d45: Pull complete
8167a8de89c3: Verifying Checksum
8167a8de89c3: Download complete
569a895c540d: Download complete
569a895c540d: Pull complete
8167a8de89c3: Pull complete
Digest: sha256:937822264394cc653444e15a65595624e358c3a8a03ecc66356af35c042b5914
Status: Downloaded newer image for circleci/ruby:2.5-node
using image circleci/ruby@sha256:937822264394cc653444e15a65595624e358c3a8a03ecc66356af35c042b5914
Error response from daemon: linux spec user: unable to find user circleci: no matching entries in passwd file
The updates can be seen here in the Docker Hub:
https://hub.docker.com/r/circleci/ruby/tags/
I tried changing to a different image just to throw a random dart at the problem but it still failed.
Thanks for any help.
- Eric