On This Page
- Why do I receive an error message when trying to use an uncertified orb?
- Why do I get the following error when testing locally?
- I receive an error when attempting to claim a namespace or publish a production orb.
- Why is my scheduled pipeline not running?
- Why are my jobs not running when I push commits?
- Why is my job queued?
- Why are my jobs queuing even though I am on the Performance plan?
- Why can I not find my project on the Projects dashboard?
- How do Docker image names work? Where do they come from?
- What is the best practice for specifying image versions?
- How can I set the timezone in Docker images?
- Container runner
- Container fails to start due to disk space
- Pod host node runs out of memory
- Pod host node is out of disk space
- The node a task is running on abruptly dies
- Image has a bad entrypoint
- Image is for a different architecture
- Bad task pod configuration
- Bash missing
- Oops, there was an issue with your infrastructure
- Machine runner
- I installed my first self-hosted runner on macOS and the job is stuck in "Preparing Environment", but there are no errors, what should I do?
- Debugging with SSH
This page offers troubleshooting suggestions for the following aspects of CircleCI:
Why do I receive an error message when trying to use an uncertified orb?
To enable usage of uncertified orbs, go to your organization’s settings page, and click the Security tab. Then, click yes to enable Allow Uncertified Orbs.
|Uncertified orbs are not tested or verified by CircleCI. Currently, only orbs created by CircleCI are considered certified. Any other orbs, including partner orbs, are not certified.|
Why do I get the following error when testing locally?
circleci build -c .circleci/jobs.yml --job test
Error: You attempted to run a local build with version 2.1 of configuration.
To resolve this error, run
circleci config process on your configuration and then save that configuration to disk. You then should run
circleci local execute against the processed configuration.
I receive an error when attempting to claim a namespace or publish a production orb.
You may not be an organization owner/admin.
Organizations can only claim a single namespace. In order to claim a namespace for an organization the authenticating user must have owner/admin privileges within the organization.
If you do not have the required permission level you might see an error similar to below:
Error: Unable to find organization YOUR_ORG_NAME of vcs-type GITHUB: Must have member permission.: the organization 'YOUR_ORG_NAME' under 'GITHUB' VCS-type does not exist. Did you misspell the organization or VCS?
Read more in the Orb CLI permissions matrix.
Why is my scheduled pipeline not running?
If your scheduled pipeline is not running, verify the following things:
Is the actor who is set for the scheduled pipelines still part of the organization? You can find this setting is under Attribution in the Triggers section of the web app.
Is the branch set for the schedule deleted?
Is your VCS organization using SAML protection? SAML tokens expire often, which can cause requests to fail.
Why are my jobs not running when I push commits?
In the CircleCI application, check the individual job and workflow views for error messages. More often than not, the error is because of formatting errors in your
See the YAML Introduction page for more details.
After checking your
.circleci/config.yml for formatting errors, search for your issue in the CircleCI support center.
Why is my job queued?
A job might end up being queued because of a concurrency limit being imposed due your organization’s plan. If your jobs are queuing often, you can consider upgrading your plan.
Why are my jobs queuing even though I am on the Performance plan?
In order to keep the system stable for all CircleCI customers, we implement different soft concurrency limits on each of the Resource classes. If you are experiencing queuing on your jobs, it is possible you are hitting these limits. Please contact CircleCI support to request raises on these limits.
Why can I not find my project on the Projects dashboard?
If you are not seeing a project you would like to build, and it is not currently building on CircleCI, check your org in the top left corner of the CircleCI application. For instance, if the top left shows your user
my-user, only projects belonging to
my-user will be available under Projects. If you want to build the project
your-org/project, you must switch your organization on the application’s organization switcher menu to
How do Docker image names work? Where do they come from?
CircleCI currently supports pulling (and pushing with Docker Engine) Docker images from Docker Hub. For official images, you can pull by simply specifying the name of the image and a tag:
For public images on Docker Hub, you can pull the image by prefixing the account or team username:
What is the best practice for specifying image versions?
It is best practice not to use the
latest tag for specifying image versions. It is also best practice to use a specific version and tag, for example
cimg/ruby:3.0.4-browsers, to pin down the image and prevent upstream changes to your containers when the underlying base distribution changes. For example, specifying only
cimg/ruby:3.0.4 could result in unexpected changes from
node. For more context, refer to Docker image best practices, and CircleCI image best practices.
How can I set the timezone in Docker images?
You can set the timezone in Docker images with the
TZ environment variable. A sample
.circleci/config.yml with a defined
TZ variable would look like the following:
version: 2.1 jobs: build: docker: - image: your/primary-image:version-tag auth: username: mydockerhub-user password: $DOCKERHUB_PASSWORD # context / project UI env-var reference - image: mysql:5.7 auth: username: mydockerhub-user password: $DOCKERHUB_PASSWORD # context / project UI env-var reference environment: TZ: "America/Los_Angeles" working_directory: ~/your-dir environment: TZ: "America/Los_Angeles"
In this example, the timezone is set for both the primary image and an additional mySQL image.
A full list of available timezone options is available on Wikipedia.
The following are errors you could encounter using container runner.
Container fails to start due to disk space
The task remains in the Preparing Environment step while the pod has a warning attached, noting that volume mounting fails due to a lack of disk space.
Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 67s default-scheduler Successfully assigned default/ccita-62e94fd3faccc34751f72803-0-7hrpk8xv to node3 Warning FailedMount 68s kubelet MountVolume.SetUp failed for volume "kube-api-access-52lfn" : write /var/snap/microk8s/common/var/lib/kubelet/pods/4cd5057f-df97-41c4-b5ef-b632ce74bf45/volumes/kubernetes.io~projected/kube-api-access-52lfn/..2022_08_02_16_24_55.1533247998/ca.crt: no space left on device
You should ensure there is sufficient disk space.
Pod host node runs out of memory
If the node a pod is hosted on runs out of memory, the task will fail with a failure step named
Runner Instance Failure, and a message:
could not run task: launch circleci-agent on "container-0" failed: command terminated with exit code 137.
The pod will have a status of
OOMKilled when viewed in Kubernetes with kubectl. You can use task pod configuration to control memory allocation for the job itself.
Pod host node is out of disk space
If the node is full it will have a
node.kuberenetes.io/disk-pressure taint, which will prevent new task pods from being scheduled. If all valid nodes for the pod have the same taint, or other conditions that prevent scheduling, the task pod will sit in a pending state until an untainted valid node becomes available. This will show the job as stuck in the Preparing Environment step in the UI.
You need to scale your cluster more effectively to avoid this state.
The node a task is running on abruptly dies
When container runner is hosted on a separate node, the task will still look like it is running in the CircleCI UI until there is a timeout for it. Kubectl will also still show the pod as running until the cluster’s liveness probe timeout is hit. The pod will then enter a terminating state that it will become wedged in. At this point the pod will need to be forcefully removed. If force is not used it may cause kubectl to hang:
kubectl delete pod $POD_NAME --force
Image has a bad entrypoint
If the entrypoint specified for the image is invalid, the task will fail with an error:
could not run task: launch circleci-agent on "container-0" failed: command terminated with exit code 139.
There is a difference between how container runner and CircleCI cloud set the entrypoint of the primary container. On cloud, the entrypoint of the primary container is ignored unless it is preserved using the
com.circleci.preserve-entrypoint=true LABEL instruction (see: Adding an entrypoint). In contrast, container runner will always default to a shell (
/bin/sh), or the entrypoint specified in the job configuration, if set.
Note: Entrypoints should be commands that run forever without failing. If the entrypoint fails or terminates in the middle of a build, the build will also terminate. If you need to access logs or build status, consider using a background step instead of an entrypoint.
Specify an entrypoint using the Adding an entrypoint documentation to mitigate this error. You can set the entrypoint explicitly as described in Using custom built Docker images.
Image is for a different architecture
If an image for a job uses a different architecture than the node it is deployed on, container runner will give an error:
19:30:12 eb1a4 11412.984ms service-work error=1 error occurred: * could not start task containers: pod failed to start: :
The task pod will also show an error status. This will show as a failed job in the CircleCI UI with the error:
could not start task containers: pod failed to start: :
You should correct the underlying architecture used for nodes with jobs to match the architecture for images being used by jobs.
Bad task pod configuration
If the task pod for a resource class is misconfigured, the task will fail once claimed. In the UI the error will be in a
Runner Instance Failure step with a message resembling:
could not start task containers: error creating task pod: Pod "ccita-62ea7dff36e977580a329a9d-0-uzz1y8xi" is invalid: [spec.containers.resources.limits[eppemeral-storage]: Invalid value: "eppemeral-storage": must be a standard resource type or fully qualified, spec.containers.resources.limits[eppemeral-storage]: Invalid value: "eppemeral-storage": must be a standard resource for containers, spec.containers.resources.requests[eppemeral-storage]: Invalid value: "eppemeral-storage": must be a standard resource type or fully qualified, spec.containers.resources.requests[eppemeral-storage]: Invalid value: "eppemeral-storage": must be a standard resource for containers]
No pod has been created in the Kuberenetes cluster. You will need to correct the task pod configuration as described on the Conatiner runner page.
"could not start task containers: exec into build container "container-0" failed: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "bb04485b9ef2386dee5e44a92bfe512ed786675611b6a518c3d94c1176f9a8aa": OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown"
Bash is required for custom images used in jobs executed with a container runner.
Oops, there was an issue with your infrastructure
If you see the message "Oops, there was an issue with your infrastructure. Verify your self-hosted runner infrastructure is operating and try re-running the job. If the issue persist, see our troubleshooting guide" on the job’s page, or if there is no content in the task lifecycle step (as shown), you should consider the potential causes described below:
Pod restart: Check if there were any container agent pod restarts around the time the workflow ran. If the pod was restarted around that time it would have resulted in the job not being processed. In such a case, we recommend rerunning the job once again.
You can check the logs for any of the previous runs using the command
kubectl logs -n circleci <full pod name> --previous.
Network connectivity issue: Check the network connectivity of the container agent, especially if the issue is intermittent. The issue can be seen when the container agent has lost network connectivity after claiming the tasks.
We suggest connecting to the pod using the command
kubectl exec --stdin --tty -n circleci < full pod name > — /bin/sh and then running a ping test for an extended period of time. We also recommend checking the connection to the links on our FAQ includes a section about the connectivity required for CircleCI’s self-hosted runners.
Resources exhaustion: Check if your pods are reaching their resources limits in the cluster, as the pod could end the job to free up resources. We recommend setting resource limits either within your values.yaml or within your config.yaml.
There are also external tools for monitoring resource usage on the Kubernetes documentation.
The following are errors you could encounter using machine runner.
I installed my first self-hosted runner on macOS and the job is stuck in "Preparing Environment", but there are no errors, what should I do?
In some cases, you may need to update the execution permission for the launch-agent so it is executable by root. Try running the following two commands:
sudo chmod +x /opt/circleci/circleci-launch-agent sudo /opt/circleci/circleci-launch-agent --config=/Library/Preferences/com.circleci.runner/launch-agent-config.yaml
Cancel the job and rerun it. If your job is still not running, file a support ticket.
Debugging with SSH
CircleCI’s machine runners support rerunning a job with SSH for debugging purposes. Instructions on using this feature can be found at Debugging with SSH.
| The |
Help make this document better
This guide, as well as the rest of our docs, are open source and available on GitHub. We welcome your contributions.
- Suggest an edit to this page (please read the contributing guide first).
- To report a problem in the documentation, or to submit feedback and comments, please open an issue on GitHub.
- CircleCI is always seeking ways to improve your experience with our platform. If you would like to share feedback, please join our research community.
Our support engineers are available to help with service issues, billing, or account related questions, and can help troubleshoot build configurations. Contact our support engineers by opening a ticket.
You can also visit our support site to find support articles, community forums, and training resources.
CircleCI Documentation by CircleCI is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.