Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitc6b9825

Browse files
committed
Add troubleshooting
1 parentf869dd9 commitc6b9825

File tree

23 files changed

+1406
-0
lines changed

23 files changed

+1406
-0
lines changed
Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
title:"Common issues"
3+
description:""
4+
group:troubleshooting
5+
redirect_from:
6+
-/docs/common-issues/
7+
-/docs/troubleshooting/
8+
toc:true
9+
---
10+
In this section, we offer helpful information about issues you may encounter and questions you might have.
11+
12+
13+
##Repository issues
14+
15+
-[Can't find your organization repositories]({{site.baseurl}}/docs/troubleshooting/common-issues/cant-find-your-organization-repositories/)
16+
-[Can't find your private repositories]({{site.baseurl}}/docs/troubleshooting/common-issues/cant-find-your-private-repositories/)
17+
-[Clone step failed]({{site.baseurl}}/docs/troubleshooting/common-issues/git-clone-step-issue/)
18+
-[Handling commit messages with quotes]({{site.baseurl}}/docs/troubleshooting/common-issues/handling-commit-messages-with-quotes/)
19+
20+
##Docker issues
21+
22+
-[The docker image does not exist or no pull access]({{site.baseurl}}/docs/troubleshooting/common-issues/the-docker-image-does-not-exist-or-no-pull-access/)
23+
-[Build step: No such file or directory]({{site.baseurl}}/docs/troubleshooting/common-issues/build-step-no-such-file-or-directory/)
24+
-[No Dockerfile found]({{site.baseurl}}/docs/troubleshooting/common-issues/no-dockerfile-found/)
25+
-[Could not tag image](could-not-tag-image)
26+
-[Failed to build image: non-zero code 137](error-code-137/)
27+
-[Error pulling image configuration: toomanyrequests](dockerhub-rate-limit/)
28+
29+
##Build/pipeline issues
30+
31+
-[Restoring data from pre-existing image hangs on]({{site.baseurl}}/docs/troubleshooting/common-issues/restoring-data-from-pre-existing-image-hangs-on/)
32+
-[Disabling codefresh caching mechanisms]({{site.baseurl}}/docs/troubleshooting/common-issues/disabling-codefresh-caching-mechanisms/)
33+
-[Pinning codefresh.yml for multi-git triggers]({{site.baseurl}}/docs/troubleshooting/common-issues/multi-git-triggers/)
34+
-[Workflow process terminated by the system]({{site.baseurl}}/docs/troubleshooting/common-issues/workflow-terminated-by-system/)
35+
-[Multi-line variable gets truncated with cf_export](cf-export-limitations)
36+
37+
##Dynamic environment issues
38+
39+
-[Validation Port warnings]({{site.baseurl}}/docs/troubleshooting/common-issues/validation-port-warnings/)
40+
41+
##Deployment issues
42+
43+
-[Forbidden Cluster Resources]({{site.baseurl}}/docs/troubleshooting/common-issues/forbidden-cluster-resources/)
44+
-[Failed to get accounts clusters during workflow]({{site.baseurl}}/docs/troubleshooting/common-issues/failed-to-get-accounts-clusters-during-workflow/)
45+
46+
##API/CLI issues
47+
48+
-[Paging does not work for images and builds]({{site.baseurl}}/docs/troubleshooting/common-issues/paging-issues-builds-images/)
49+
50+
51+
52+
53+
54+
55+
Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
title:"Build step: No such file or directory"
3+
description:""
4+
group:troubleshooting
5+
sub_group:common-issues
6+
permalink:/:collection/troubleshooting/common-issues/build-step-no-such-file-or-directory/
7+
redirect_from:
8+
-/docs/build-step-no-such-file-or-directory/
9+
toc:true
10+
---
11+
12+
##Issue
13+
14+
Following error in the logs of the build step:
15+
16+
`Text`
17+
{% highlight text %}
18+
Step 3/6 : COPY /output /app
19+
lstat output: no such file or directory
20+
{% endhighlight %}
21+
22+
##Possible cause
23+
This issue generally occurs if you use an incorrect path to the Dockerfile or to the Build context.
24+
25+
##Solution
26+
Recheck, and use the correct path to Dockerfile and Build context
27+
28+
{:start="1"}
29+
1. The path to Dockerfile.
30+
31+
{:start="2"}
32+
2. The path to Build context.
33+
**Build context** is where we can find your Dockerfile as well as running commands. Your Dockerfile must be relative to this directory.
34+
35+
{% include
36+
image.html
37+
lightbox="true"
38+
file="/images/troubleshooting/no_such_file_directory.png"
39+
url="/images/troubleshooting/no_such_file_directory.png"
40+
alt="codefresh_no_such_file_directory.png"
41+
max-width="40%"
42+
%}
43+
44+
{{site.data.callout.callout_info}}
45+
In case with codefresh.yml, to specify the path to build context you need to use`working_directory`
46+
{{site.data.callout.end}}
47+
48+
`build step`
49+
{% highlight yaml %}
50+
step_name:
51+
type: build
52+
title: Step Title
53+
description: Free text description
54+
working_directory: path/to/buildcontext
55+
dockerfile: path/to/Dockerfile
56+
image_name: owner/new-image-name
57+
tag: develop
58+
{% endhighlight %}
59+
60+
##Related articles
61+
[Troubleshooting common issues]({{site.baseurl}}/docs/troubleshooting/common-issues)
Lines changed: 116 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,116 @@
1+
---
2+
title:"Can't find your organization repositories"
3+
description:"Issues with adding Git triggers"
4+
group:troubleshooting
5+
sub_group:common-issues
6+
redirect_from:
7+
-/docs/cant-find-your-organization-repos/
8+
toc:true
9+
---
10+
##Issue
11+
12+
Unable to find the GitHub organization to with the repository to which to add a[git trigger]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/).
13+
14+
{% include
15+
image.html
16+
lightbox="true"
17+
file="/images/troubleshooting/cannot-find-repo.png"
18+
url="/images/troubleshooting/cannot-find-repo.png"
19+
alt="Repository not found"
20+
max-width="60%"
21+
caption="Repository not found"
22+
%}
23+
24+
###Solution
25+
26+
1. Navigate to your GitHub user settings page:
27+
1. Log in to GitHub using your credentials.
28+
1. Navigate to your*Settings* page.
29+
30+
{% include
31+
image.html
32+
lightbox="true"
33+
file="/images/troubleshooting/github-user-menu.png"
34+
url="/images/troubleshooting/github-user-menu.png"
35+
alt="GitHub user menu"
36+
max-width="40%"
37+
caption="GitHub user menu"
38+
%}
39+
40+
{:start="2"}
41+
1. Navigate to your Authorized applications:
42+
In your*Personal settings* view, click*Authorized applications*.
43+
44+
{% include
45+
image.html
46+
lightbox="true"
47+
file="/images/troubleshooting/personal-settings.png"
48+
url="/images/troubleshooting/personal-settings.png"
49+
alt="Personal settings"
50+
max-width="40%"
51+
caption="Personal settings"
52+
%}
53+
54+
{:start="3"}
55+
1. Locate and click the Codefresh authorized application.
56+
57+
{% include
58+
image.html
59+
lightbox="true"
60+
file="/images/troubleshooting/authorized-applications.png"
61+
url="/images/troubleshooting/authorized-applications.png"
62+
alt="Authorized applications"
63+
max-width="40%"
64+
caption="Authorized applications"
65+
%}
66+
67+
{:start="4"}
68+
1. In the Organization access section find your organization.
69+
1. If you_do not have Admin privileges for your organization_, click**Request access**, to request the necessary privileges from your administrator.
70+
71+
{% include
72+
image.html
73+
lightbox="true"
74+
file="/images/troubleshooting/request-access-to-codefresh-app.png"
75+
url="/images/troubleshooting/request-access-to-codefresh-app.png"
76+
alt="Request access"
77+
max-width="40%"
78+
caption="Request access"
79+
%}
80+
81+
{% include
82+
image.html
83+
lightbox="true"
84+
file="/images/troubleshooting/access-requested.png"
85+
url="/images/troubleshooting/access-requested.png"
86+
alt="Access requested"
87+
max-width="40%"
88+
caption="Access requested"
89+
%}
90+
91+
{:start="6"}
92+
1. If_you are an organization administrator_, click**Grant access**.
93+
You always have the option to revoke access.
94+
95+
{% include
96+
image.html
97+
lightbox="true"
98+
file="/images/troubleshooting/non-admin-grant-access.png"
99+
url="/images/troubleshooting/non-admin-grant-access.png"
100+
alt="Grant access"
101+
max-width="40%"
102+
caption="Grant access"
103+
%}
104+
105+
{% include
106+
image.html
107+
lightbox="true"
108+
file="/images/troubleshooting/non-admin-access-granted.png"
109+
url="/images/troubleshooting/non-admin-access-granted.png"
110+
alt="Access granted"
111+
max-width="40%"
112+
caption="Access granted"
113+
%}
114+
115+
##Related articles
116+
[Troubleshooting common issues]({{site.baseurl}}/docs/troubleshooting/common-issues)
Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
title:"Can't find private repositories"
3+
description:""
4+
group:troubleshooting
5+
sub_group:common-issues
6+
redirect_from:
7+
-/docs/cant-find-your-private-repositories/
8+
toc:true
9+
---
10+
##Issue
11+
I want to add a private repository to Codefresh but can't find it in the repository list.
12+
13+
{% include
14+
image.html
15+
lightbox="true"
16+
file="/images/troubleshooting/private-repos.png"
17+
url="/images/troubleshooting/private-repos.png"
18+
alt="Adding private repositories"
19+
caption="Adding private repositories"
20+
max-width="60%"
21+
%}
22+
23+
##Possible cause
24+
This means that you haven’t granted Codefresh permission to access private repositories.
25+
26+
##Solution
27+
Click the link on the right that says "private repositories".
28+
29+
You can also enable the same thing from the user settings page:
30+
31+
{% include
32+
image.html
33+
lightbox="true"
34+
file="/images/troubleshooting/allow-private-repositories.png"
35+
url="/images/troubleshooting/allow-private-repositories.png"
36+
alt="Allow private repositories"
37+
caption="Allow private repositories"
38+
max-width="70%"
39+
%}
40+
41+
42+
>Some Git providers redirect you to the provider’s permission page.
43+
44+
##Related articles
45+
[Troubleshooting common issues]({{site.baseurl}}/docs/troubleshooting/common-issues)
Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
---
2+
title:"Multiline variable gets truncated with cf_export"
3+
description:"Exporting multiline variables to subsequent pipeline steps"
4+
group:troubleshooting
5+
sub_group:common-issues
6+
toc:true
7+
---
8+
9+
10+
11+
12+
##Issue
13+
Exporting a multi-line variable with`cf_export` within a pipeline truncates the variable.
14+
15+
Running the pipeline in the example below, in the step`test` the value of the variable is truncated and only`line1` will appear.
16+
17+
{% highlight yaml %}
18+
{% raw %}
19+
version: "1.0"
20+
steps:
21+
assign:
22+
image: alpine
23+
commands:
24+
- export TEST=`echo "line1" && echo "line2" && echo "line3"`
25+
- echo $TEST
26+
- cf_export TEST
27+
test:
28+
image: alpine
29+
commands:
30+
- echo $TEST
31+
{% endraw %}
32+
{% endhighlight %}
33+
34+
Every Codefresh pipeline has access to the that allows you to pass[environment variables]({{site.baseurl}}/docs/codefresh-yaml/variables/) from[one step to the next].
35+
36+
##Solution
37+
38+
Encode the variable with`base64` to handle all special characters in the exported variable.
39+
40+
{% highlight yaml %}
41+
{% raw %}
42+
version: "1.0"
43+
steps:
44+
assign:
45+
image: alpine
46+
commands:
47+
- apk add --update coreutils
48+
- export TEST=`echo "line1" && echo "line2" && echo "line3"`
49+
- echo $TEST
50+
- cf_export TEST=`echo $TEST | base64 -w 0`
51+
test:
52+
image: alpine
53+
commands:
54+
- echo $TEST
55+
- echo`echo $TEST | base64 -d`
56+
{% endraw %}
57+
{% endhighlight %}
58+
59+
If you run this pipeline, the`test` step will correctly print`line1 line2 line3`
60+
61+
62+
63+
##Related articles
64+
[cf_export utility in pipelines]({{site.baseurl}}/docs/pipelines/variables/#using-cf_export-command)
65+
[Passing variables between steps]({{site.baseurl}}/docs/pipelines/introduction-to-codefresh-pipelines/#using-docker-containers-as-build-tooling)
66+
[Troubleshooting common issues]({{site.baseurl}}/docs/troubleshooting/common-issues)
67+
68+
69+
70+
71+
Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
title:"Failed to tag image"
3+
description:"Failed to update your image with promote event, could not tag image"
4+
group:troubleshooting
5+
sub_group:common-issues
6+
toc:true
7+
---
8+
9+
##Issue
10+
[Push step]({{site.baseurl}}/docs/codefresh-yaml/steps/push/) in your pipeline fails with the following error:
11+
12+
13+
```
14+
[SYSTEM] Error: Failed to push image docker.io/example/my-image:1.0.0; caused by Error: Failed to update your image with promote event; caused by Error: NotFoundError: could not tag image
15+
```
16+
17+
##Possible cause
18+
19+
This issue occurs because of a race condition when multiple builds try to push the same image at the same time[to a Docker registry]({{site.baseurl}}/docs/docker-registries/push-image-to-a-docker-registry/).
20+
For a pipeline, if two builds are triggered at the same time for the same commit, one of them will pass and the other will fail.
21+
22+
##Solution
23+
24+
Review the trigger setup according to the pipeline logic, and verify that is triggered only once when an event happens.
25+
26+
It is not possible to push the same image at the same time to the same registry. Your pipeline configuration has probably[multiple triggers]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/) (such as a commit and tag) that trigger the pipeline twice.
27+
28+
##Related articles
29+
[Troubleshooting common issues]({{site.baseurl}}/docs/troubleshooting/common-issues)
30+

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp