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 cir…

Update: The issue has been identified and fix applied. New images are already being published, but it will take a few hours to get through them all. – Thank you all for reporting. ▶ Original Status ▶ Workaround

We’re seeing this error as well, on the circleci/ruby:2.3.8-node docker image. We have a different project using circleci/ruby:2.5.1-node-browsers that doesn’t seem to be affected, but that might just be caching at work.

I’m seeing the exact same thing with the circleci/golang:1.11.2-node image.

Biting us right now too - this is frustrating…

We’ve got a workaround - pin to the last working docker image sha256. You can grab that from the “spin up environment” step of the last successful build, then just include is in your circle config. This is what we’re using for ruby-2.3.8-node-browsers: image: circleci/ruby@sha256:be06794b34768076a…

We’re using Ruby 2.5.3, but seeing it when we start the redis image (which apparently happens before rails) Build-agent version 0.1.1073-1f69f340 (2018-11-20T18:07:03+0000) Starting container circleci/ruby:2.5.3-node image is cached as circleci/ruby:2.5.3-node, but refreshing... 2.5.3-node: Pulli…

Same here. Reproducible on my Mac: ✗ docker run circleci/python:2.7.15-node docker: Error response from daemon: linux spec user: unable to find user circleci: no matching entries in passwd file. ERRO[0000] error waiting for container: context canceled

We have the same problem as well, pulling from circleci/ruby:2.5.3-node (circleci/ruby@sha256:937822264394cc653444e15a65595624e358c3a8a03ecc66356af35c042b5914) and circleci/postgres:9.6-alpine-ram (circleci/postgres@sha256:6bde827b91b15d6250882ca6610f43570e89ef3a5db842b052c2201415cc7554).

Seeing this too. I can confirm that specifying the sha in config.yml for the ruby image (I got mine from the output of my last successful CI run) mitigates the issue for now.

Docker images unable to find circleci user

Feedback & Bug Reports

jesse.vh November 27, 2018, 10:24pm 11

CircleCI support recommended the sha pinning as a workaround, and said they’re working on it.

Image circleci/php:5.6-apache-node doesn't work anymore

Topic		Replies	Views
Image circleci/php:5.6-apache-node doesn't work anymore Build Environment	12	2382	November 28, 2018
Error response from daemon: manifest for circleci/android:api-25-alpha not found Build Environment docker , convenience-images	20	11208	August 17, 2018
Circleci-builder error Feedback & Bug Reports	5	1798	April 10, 2017
Can't get CI to use latest Docker image Build Environment	8	3265	October 28, 2018
Caching docker images is not working Caching Dependencies	7	10132	August 20, 2018

Docker images unable to find circleci user

Related topics