Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
G
gitlab-runner
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Lars Seipel
gitlab-runner
Commits
dae928f9
Commit
dae928f9
authored
6 years ago
by
Jacob Embree
Browse files
Options
Downloads
Patches
Plain Diff
Update advanced-configuration.md: Fix blockquote not reaching the entire note
parent
997689e2
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/configuration/advanced-configuration.md
+3
-3
3 additions, 3 deletions
docs/configuration/advanced-configuration.md
with
3 additions
and
3 deletions
docs/configuration/advanced-configuration.md
+
3
−
3
View file @
dae928f9
...
...
@@ -299,12 +299,12 @@ This will use `/path/to/bind/from/host` of the CI host inside the container at
### Using a private container registry
> **Notes:**
-
This feature requires GitLab Runner
**1.8**
or higher
-
For GitLab Runner versions
**>= 0.6, <1.8**
there was a partial
>
- This feature requires GitLab Runner **1.8** or higher
>
- For GitLab Runner versions **>= 0.6, <1.8** there was a partial
support for using private registries, which required manual configuration
of credentials on runner's host. We recommend to upgrade your Runner to
at least version
**1.8**
if you want to use private registries.
-
Using private registries with the
`if-not-present`
pull policy may introduce
>
- Using private registries with the `if-not-present` pull policy may introduce
[
security implications
][
secpull
]
. To fully understand how pull policies work,
read the
[
pull policies documentation
](
../executors/docker.md#how-pull-policies-work
)
.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment