url:"/no-dockerfile-found"

-title:Could not tag image

url:"/could-not-tag-image"

-title:Failed to create container of image

url:"/create-container-failure"

-title:Error Code 137

url:"/error-code-137"

-title:Too many Requests

{: .table .table-bordered .table-hover}

| Item| Requirement|

| --------------| --------------|

|Container runtime| Any compliant container runtime, as the runner is**not** dependent on any special dockershim features. {::nomarkdown}<br>Examples: <ul><li><ahref="https://kubernetes.io/blog/2020/12/02/dockershim-faq"target="blank">Docker</a></li><li><ahref="https://containerd.io/"target="blank">containerd</a></li><li><ahref="https://cri-o.io/"target="blank">cri-o</a></li></ul> {:/}|

|CLI token|[Codefresh CLI token]({{site.baseurl}}/docs/integrations/codefresh-api/#authentication-instructions)|

Install the Runner from any workstation or laptop with access to the Kubernetes cluster running Codefresh builds, via`kubectl`. The Codefresh Runner authenticates to your Codefresh account using the CLI token.

Here you can define global template behavior. The options are:

* Enable[pipeline templates]({{site.baseurl}}/docs/docs/configure-ci-cd-pipeline/pipelines/#using-pipeline-templates) for users. If this is enabled some pipelines can be marked as templates and users can still select them when creating a new pipeline.

* Decide if users can clone an existing pipeline (along with its triggers and associated parameters) when[creating a new pipeline]({{site.baseurl}}/docs/docs/configure-ci-cd-pipeline/pipelines/#creating-new-pipelines).

* Enable[pipeline templates]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#using-pipeline-templates) for users. If this is enabled some pipelines can be marked as templates and users can still select them when creating a new pipeline.

* Decide if users can clone an existing pipeline (along with its triggers and associated parameters) when[creating a new pipeline]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#creating-new-pipelines).

Note that templates are simply normal pipelines “marked” as a template. There is no technical difference between templates and actual pipelines.

Here you can restrict the sources of pipeline YAML that users can select. The options are:

* Enable/Disable the[inline editor]({{site.baseurl}}/docs/docs/configure-ci-cd-pipeline/pipelines/#using-the-inline-pipeline-editor) where YAML is stored in Codefresh SaaS

* Enable/Disable the[inline editor]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#using-the-inline-pipeline-editor) where YAML is stored in Codefresh SaaS

* Enable/disable pipeline YAML from connected Git repositories

* Enable/disable pipeline YAML from[external URLs]({{site.baseurl}}/docs/docs/configure-ci-cd-pipeline/pipelines/#loading-codefreshyml-from-version-control)

* Enable/disable pipeline YAML from[external URLs]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#loading-codefreshyml-from-version-control)

You need to allow at least one of these options so that users can create new pipelines. We suggest leaving the first option enabled when users are still learning about Codefresh and want to experiment.

2. All built images are automatically pushed to the default registry

3. All built images are NOT pushed anywhere by default

Note that this behavior is simply a convenience feature for legacy pipelines. Users can still use a[push step]({{site.baseurl}}/docs/docs/codefresh-yaml/steps/push/) in a pipeline and always push an image to a registry regardless of what was chosen in the build step.

Note that this behavior is simply a convenience feature for legacy pipelines. Users can still use a[push step]({{site.baseurl}}/docs/codefresh-yaml/steps/push/) in a pipeline and always push an image to a registry regardless of what was chosen in the build step.

*[Creating Pipelines]({{site.baseurl}}/docs/docs/configure-ci-cd-pipeline/pipelines/)

*[Codefresh YAML]({{site.baseurl}}/docs/docs/codefresh-yaml/what-is-the-codefresh-yaml/)

*[Git Integration]({{site.baseurl}}/docs/docs/integrations/git-providers/)

*[Creating Pipelines]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/)

*[Codefresh YAML]({{site.baseurl}}/docs/codefresh-yaml/what-is-the-codefresh-yaml/)

*[Git Integration]({{site.baseurl}}/docs/integrations/git-providers/)

Codefresh offers several metrics for pipelinesteps that allow you to get a better overviewon the resources

Codefresh offers several metrics forthepipeline, and forstepsin the pipeline,that allow you to get a better overviewof the resources

consumed by your pipeline.

At the most basic level Codefresh will show some quick metrics while the pipeline is running that include

**Pipeline metrics**

At the most basic level, Codefresh displays quick metrics while the pipeline is running that include

memory consumed and size of logs:

{% include

image.html

lightbox="true"

file="/images/pipeline/monitoring/quick-pipeline-metrics.png"

url="/images/pipeline/monitoring/quick-pipeline-metrics.png"

alt="Pipelinerunningmetrics"

caption="Pipelinerunningmetrics"

max-width="70%"

alt="Metrics forrunningpipeline"

caption="Metrics forrunningpipeline"

max-width="95%"

%}

You can then get the memory usage for the whole pipeline by clicking on the metrics tab at the bottom of the screen.

* To view memory and disk usage for running or completed pipeline builds, click the**Metrics** tab at the bottom of the Build page.

* Memory usage: View memory usage (Y-axis) by time (X-axis) for the duration of the build.

* Disk usage: View disk usage (Y-axis) by time (X-axis) for the duration of the build. The red line is set at 90% of the maximum disk space.

To see the precise usage at different points in time, mouse over the dots.

Viewing the actual disk usage for a build during its run allows you to better gauge and define the[minimum disk space required for the build volume]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#runtime).

{% include

image.html

lightbox="true"

file="/images/pipeline/monitoring/pipeline-metrics.png"

url="/images/pipeline/monitoring/pipeline-metrics.png"

alt="Pipeline detailedmetrics"

caption="Pipeline detailedmetrics"

max-width="70%"

alt="Detailedmetrics for pipelines"

caption="Detailedmetrics for pipelines"

max-width="60%"

%}

If you click on an individual step before clicking the*Metrics* tab you will get metrics for that specific step only.

**Pipeline-step metrics**

For step-specific metrics, first select the step, and then click the**Metrics** tab.

Step metrics are available for memory and CPU usage (not disk space).

{% include

**Q. Is Codefresh open-source?**

A. The Web UI is not open source. All the[pipeline plugins](https://codefresh.io/steps/) and the[Codefresh Runner]({{site.baseurl}}/docs/enterprise/codefresh-runner/) are open-source. We also publish several open-source[components](https://github.com/codefresh-io),[examples](https://github.com/codefresh-contrib) and[demos](https://github.com/codefreshdemo/).

**Q. How is pricing structured?**

A. Pricing is per concurrent build. In practice this means how many pull requests you can process*at the same time*. See the[pricing page](https://codefresh.io/pricing/) for more details.

**Q. Is there a pay as you go model?**

A. We are always considering new pricing options. The pay as you go model has flaws as well. One of the big selling points of Codefresh is the different types of caches we employ in order to speed up builds. When a company charges for build minutes, it has no further motivation to cut down on build times. Several CI solutions offer no caching mechanisms, forcing you to download application dependencies on each build. Please contact us to discuss about pricing if this is your main blocker from adopting Codefresh.

**Q. Does Codefresh offer infrastructure for running builds?**

A. Yes, the cloud version of Codefresh is fully[SAAS](https://en.wikipedia.org/wiki/Software_as_a_service). You only need to open an account and all builds are running on our cloud. You can still use a[Codefresh runner]({{site.baseurl}}/docs/enterprise/codefresh-runner/) to run builds on your own infrastructure, but this is completely optional.

-[Pinning codefresh.yml for multi-git triggers]({{site.baseurl}}/docs/troubleshooting/common-issues/multi-git-triggers/)

-[Workflow process terminated by the system]({{site.baseurl}}/docs/troubleshooting/common-issues/workflow-terminated-by-system/)

-[Multi-line variable gets truncated with cf_export](cf-export-limitations)

-[Failed to create container of image]({{site.baseurl}}/docs/troubleshooting/common-issues/create-container-failure)

title:"Failed to create container of image"

description:"Failure creating container"

group:troubleshooting

sub_group:common-issues

toc:true

Freestyle step fails with message:`Failed to create a container of: <image>`

This issue occurs if your image filesystem already contains a_file_ in`/codefresh` or`/codefresh/volume`. The Codefresh engine cannot mount the Codefresh volume within a_file_.

Make sure that the filesystem does not contain files entitled`codefresh`, and that the`/codefresh/volume` directory can be created successfully.

toc:true

- Set disk space for a pipeline build volume -[documentation]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#runtime)

- Support for latest Kubernetes cluster version 1.24 -[documentation]({{site.baseurl}}/docs/administration/codefresh-runner/#prerequisites)