public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-15 17:43:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix pipeline doc -- image in internal registry can only be used inside the pipeline

Browse Source
This commit is contained in:
Sheng Liang
2018-09-29 20:47:40 -07:00
committed by Denise
parent 4015ebdfe0
commit 3ef973976b
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/tools/pipelines/_index.md
+1 -1
View File
@@ -65,7 +65,7 @@ When you configure a pipeline in one of your projects, a namespace specifically
- **Docker Registry:**
Out-of-the-box, the default target for your build-publish step is an internal Docker Registry. However, you can make configurations to push to a remote registry instead. The internal Docker Registry is only accessible from cluster nodes and cannot be directly accessed by users. Images are not persisted across multiple pipeline runs. If you need to access your images outside of a single pipeline run, please push to an external registry.
Out-of-the-box, the default target for your build-publish step is an internal Docker Registry. However, you can make configurations to push to a remote registry instead. The internal Docker Registry is only accessible from cluster nodes and cannot be directly accessed by users. Images are not persisted beyond the lifetime of the pipeline and should only be used in pipeline runs. If you need to access your images outside of pipeline runs, please push to an external registry.
<a id="minio"></a>