Error during "Spin up Environment" step showing status of "Circle Bug"

Feedback & Bug Reports
1

We seem to be having some issues deploying our latest develop branch with CircleCI. We had a successful deployment yesterday but then today with same CircleCI configs we are getting an error while trying to spin up the environment. We noticed that the build-agent has been updated, not sure if that’s related or not. I inherited this deployment process so I’ve just barely scratched the surface of the CircleCI setup.

We did try removing command: /sbin/init from our config.yml file per https://support.circleci.com/hc/en-us/articles/360013144894-Resolving-CircleCI-was-unable-to-start-the-container- which got us past the environment spin up, but then it fails to connect to the database and command: /sbin/init has been in the config for almost a year so not sure why it would stop working all the sudden.

Also not really sure why it’s tagging the builds as “Circle Bug” does that indicate that it has determined an error on the CircleCI side?

Any help would be appreciated at this point!

2

Last successful build was with:
Build-agent version 1.0.12984-91e3a18a (2019-08-09T14:05:07+0000)

All the failed builds were with:
Build-agent version 1.0.13455-a66ea3ac (2019-08-12T21:51:13+0000)

If that matters…

3

Oh, and it might help to have the error too:

Unexpected environment preparation error: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:303: getting the final child's pid from pipe caused \"EOF\"": unknown
4

We were experiencing something similar, CircleCI was unable to run the job runner appears to have gotten us past where the DB not starting was derailing our previous builds.

5

Indeed that did it for us too, totally missed that post, thanks!