Day 8: Private Registries and Credentials
Goal: Renovate finds updates for a private npm package and a private container image without a token ending up in the repo. · Duration: approx. 120 min · Prerequisite: Day 3
Briefing
- Forgejo comes with a package registry for npm, container images, and other formats. It is attached to org or user accounts and inherits their visibility.
- Without credentials, a lookup does not abort. Renovate reports “Failed to look up” in the Dependency Dashboard and carries on with the rest.
- You give Renovate credentials via
hostRules. These rules belong in the operator’s global config, not in the repo. - If a repo wants its own
hostRules, it refers with{{ secrets.NAME }}to values that only the operator knows.
renovate.json ──► hostRules: matchHost + hostType ──► token from global config
│
package.json ─► npm lookup ─► 127.0.0.1:3000/api/packages/shop/npm/ ◄┤
cron.Dockerfile ─► docker lookup ─► 127.0.0.1:3000/v2/shop/base ◄────┘
Drill 1: A private npm package
Fresh state, then a token for lab-admin that may write
packages. You set the org shop to limited:
only signed-in users see it and its packages.
source ~/renovate-lab/setup/env.sh
curl -s -o /dev/null -w '%{http_code}\n' -u "$ADMIN" \
-X DELETE "$FORGEJO/api/v1/repos/shop/shop-api"
git -C ~/renovate-lab/shop-api push -q forgejo:shop/shop-api.git main
mkdir -p ~/renovate-lab/tag08 && cd ~/renovate-lab/tag08
docker exec forgejo forgejo admin user generate-access-token --username lab-admin \
--token-name "packages-$(date +%s)" --scopes write:package --raw > pkg-token
chmod 600 pkg-token
curl -s -u "$ADMIN" -X PATCH --json '{"visibility":"limited"}' \
"$FORGEJO/api/v1/orgs/shop" | jq -r .visibilityExpected:
204
limited
The package @shop/money is in the companion code. For
publishing, npm uses a separate configuration file. Your
~/.npmrc stays untouched.
cp -R ~/renovate-lab/code/tag08/money .
cat > publish.npmrc <<EOF
@shop:registry=$FORGEJO/api/packages/shop/npm/
${FORGEJO#http:}/api/packages/shop/npm/:_authToken=$(cat pkg-token)
EOF
chmod 600 publish.npmrc
npm publish ./money --userconfig publish.npmrc 2>&1 | tail -2
curl -s -o /dev/null -w "anonym: %{http_code}\n" \
"$FORGEJO/api/packages/shop/npm/@shop%2fmoney"
curl -s -H "Authorization: token $RENOVATE_TOKEN" \
"$FORGEJO/api/packages/shop/npm/@shop%2fmoney" \
| jq -c '{name, versions: (.versions | keys)}'Expected (shortened):
npm notice Publishing to http://127.0.0.1:3000/api/packages/shop/npm/ with tag latest
+ @shop/[email protected]
anonym: 401
{"name":"@shop/money","versions":["1.0.0"]}
Anonymously (anonym), the package is locked. The bot
reads it with its normal token: since Day 0 it has had the scope
read:package, and as a signed-in user it sees a
limited org. A separate registry token for Renovate is not
needed here.
Security:
pkg-tokenandpublish.npmrccontain a write token. It belongs to the release process, never to Renovate. Renovate only needs read access.
Save your progress? Sign up for free
Drill 2: A private container image
Docker talks to registries on 127.0.0.1 even without
TLS. The base image shop/base is built from
alpine and gets a version label.
REG=127.0.0.1:3000
docker login $REG -u lab-admin --password-stdin < pkg-token 2>&1 | tail -1
docker image inspect alpine:latest >/dev/null 2>&1 || docker pull -q alpine:latest
echo "FROM alpine:latest" | docker build -q \
--label org.opencontainers.image.version=1.0.0 -t $REG/shop/base:1.0.0 - 2>/dev/null
docker push -q $REG/shop/base:1.0.0
curl -s -o /dev/null -w "anonym: %{http_code}\n" "$FORGEJO/v2/shop/base/tags/list"
curl -s -u "$ADMIN" "$FORGEJO/api/v1/packages/shop" \
| jq -r '.[] | "\(.type)\t\(.name)\t\(.version)"'Expected (image ID shortened):
Login Succeeded
sha256:ac7bdaa911a5…
127.0.0.1:3000/shop/base:1.0.0
anonym: 401
container base 1.0.0
npm @shop/money 1.0.0
The image name 127.0.0.1:3000/shop/base follows from
Forgejo’s ROOT_URL. The login ends up in
~/.docker/config.json (or in the keychain). At the end of
the day you log out again.
Save your progress? Sign up for free
Drill 3: shop-api uses both
The repo gets an .npmrc with the scope registry (without
a token), a cron.Dockerfile based on
shop/base, and a renovate.json that today only
looks at the internal packages.
R="$FORGEJO/api/v1/repos/shop/shop-api"
rm -rf shop-api
git clone -q forgejo:shop/shop-api.git
cd shop-api
cp ~/renovate-lab/code/tag08/shop-api/{.npmrc,cron.Dockerfile,renovate.json} .
cat .npmrc cron.Dockerfile
npm install --userconfig ../publish.npmrc --save-exact --no-fund --no-audit \
@shop/[email protected]
grep -A2 '"node_modules/@shop/money"' package-lock.json | cut -c1-88
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "Interne Pakete einbinden"
git push -q origin mainExpected:
@shop:registry=http://127.0.0.1:3000/api/packages/shop/npm/
FROM 127.0.0.1:3000/shop/base:1.0.0
CMD ["echo", "Nachtlauf"]
added 71 packages in 2s
"node_modules/@shop/money": {
"version": "1.0.0",
"resolved": "http://127.0.0.1:3000/api/packages/shop/npm/%40shop%2Fmoney/-/1.0.0/
The renovate.json (companion code):
{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": ["config:recommended"],
"prHourlyLimit": 0,
"packageRules": [
{
"description": "Heute nur die internen Pakete der Org shop",
"matchPackageNames": ["!@shop/**", "!**/shop/base"],
"enabled": false
}
]
}A list consisting only of negations matches everything that is not
excluded (Day 2). The file name cron.Dockerfile matches the
default pattern of the dockerfile manager.
Save your progress? Sign up for free
Drill 4: What failure looks like without credentials
renovate shop/shop-api 2>&1 | grep -E "^ (WARN|ERROR)|Failed to look up" | cut -c1-88
curl -s -u "$ADMIN" "$R/issues?type=issues" \
| jq -r '.[] | select(.title == "Dependency Dashboard") | .body' > dashboard.md
grep -A6 '^## Repository Problems' dashboard.md | cut -c1-88Expected:
WARN: HTTP request to an internal host, which `internalHostAccess=block` would refu
WARN: Error obtaining docker token (repository=shop/shop-api)
WARN: Package lookup failures (repository=shop/shop-api)
"Failed to look up docker package 127.0.0.1:3000/shop/base: no-result",
"Failed to look up npm package @shop/money: no-result"
## Repository Problems
Renovate tried to run on this repository, but found these problems.
- ⚠️ WARN: HTTP request to an internal host, which `internalHostAccess=block` would ref
- ⚠️ WARN: Error obtaining docker token
---
> ⚠️ **Warning**
>
> Renovate failed to look up the following dependencies: `Failed to look up docker packa
>
> Files affected: `cron.Dockerfile`, `package.json`
---
This repository currently has no open or pending branches.
No abort, no PR, but a clear notice in the Dashboard. The debug log shows exactly why:
LOG_LEVEL=debug renovate shop/shop-api > ../debug-1.log 2>&1
grep -E "statusCode=" ../debug-1.log \
| sed -E 's/.*GET ([^ ]+) .*statusCode=(-?[0-9]+).*/\2 \1/'
grep -o "wrong version number" ../debug-1.log | head -1Expected:
-1 https://127.0.0.1:3000/v2/shop/base/tags/list?n=10000
401 http://127.0.0.1:3000/api/packages/shop/npm/@shop%2Fmoney
wrong version number
Two different errors. npm gets a clean 401. The Docker datasource
always assumes https:// for registries without a scheme and
fails at the TLS handshake with an HTTP server. In the lab, that needs
insecureRegistry (Drill 5); in production, never.
The second warning concerns internalHostAccess: Renovate
warns about requests to loopback and private addresses and wants to
block them by default in a later major version. A hostRules
rule that names the host allows it.
Warning: You will not see the issue “Action Required: Add missing credentials” here. Renovate 44 creates it only when credentials for Merge Confidence (Mend API) are missing. Missing registry credentials appear only in the Dashboard and in the log.
Save your progress? Sign up for free
Drill 5: hostRules via environment variable
First the obvious attempt: a rule with host and port, without
hostType.
export RENOVATE_HOST_RULES='[{"matchHost": "127.0.0.1:3000",
"token": "'"$RENOVATE_TOKEN"'"}]'
LOG_LEVEL=debug renovate shop/shop-api > ../debug-2.log 2>&1
grep -E "authentication for (https://)?127|statusCode=" ../debug-2.log | sort -u \
| sed -E 's/.*GET ([^ ]+) .*statusCode=(-?[0-9]+).*/\2 \1/; s/ \(repository=.*//' \
| cut -c1-88Expected:
DEBUG: Adding token authentication for 127.0.0.1 (hostType=forgejo) to hostRules
DEBUG: Adding token authentication for https://127.0.0.1:3000 (hostType=undefined) to ho
401 http://127.0.0.1:3000/api/packages/shop/npm/@shop%2Fmoney
-1 https://127.0.0.1:3000/v2/shop/base/tags/list?n=10000
Still 401. From a matchHost with a port or path but
without a scheme, Renovate makes the URL
https://127.0.0.1:3000. Renovate compares a URL in
matchHost as a prefix, and http://… does not
start with https://….
matchHost |
matches |
|---|---|
127.0.0.1 |
any port, any scheme on this hostname |
127.0.0.1:3000 |
only https://127.0.0.1:3000… |
http://127.0.0.1:3000/api/packages/ |
only URLs with exactly this prefix |
So you build two matching rules: npm by URL prefix with a token,
Docker by hostname with username and password plus
insecureRegistry. jq -n generates the JSON,
and --arg inserts the token without it ending up in a
file:
export RENOVATE_HOST_RULES=$(jq -nc --arg t "$RENOVATE_TOKEN" '[
{matchHost: "http://127.0.0.1:3000/api/packages/", hostType: "npm", token: $t},
{matchHost: "127.0.0.1", hostType: "docker", username: "renovate-bot",
password: $t, insecureRegistry: true}
]')
echo "$RENOVATE_HOST_RULES" | jq -c '.[] | {matchHost, hostType}'
renovate shop/shop-api 2>&1 | grep -cE "^ WARN"
curl -s -u "$ADMIN" "$R/issues?type=issues" \
| jq -r '.[] | select(.title == "Dependency Dashboard") | .body' > dashboard.md
grep -cE "Repository Problems|failed to look up" dashboard.md
grep -- ' - `' dashboard.mdExpected:
{"matchHost":"http://127.0.0.1:3000/api/packages/","hostType":"npm"}
{"matchHost":"127.0.0.1","hostType":"docker"}
0
0
- `127.0.0.1:3000/shop/base 1.0.0`
- `@shop/money 1.0.0`
No more warnings, the Dashboard is clean, and both dependencies are
detected. There is just no newer version yet. hostType
keeps the rules apart: the Docker rule does not apply to npm or to the
Forgejo API, even though all three point to 127.0.0.1.
Tip: The Forgejo container registry requires a bearer token, which Renovate fetches itself with
username/password(“applying Bearer authentication” in the debug log). A token as the password is enough; never the bot’s login password.
Save your progress? Sign up for free
Drill 6: New versions, new PRs
Publish version 1.1.0 of both packages, then run Renovate.
cd ~/renovate-lab/tag08
npm version 1.1.0 --prefix money --no-git-tag-version
npm publish ./money --userconfig publish.npmrc 2>&1 | tail -1
echo "FROM alpine:latest" | docker build -q \
--label org.opencontainers.image.version=1.1.0 -t $REG/shop/base:1.1.0 - 2>/dev/null
docker push -q $REG/shop/base:1.1.0
cd shop-api
LOG_LEVEL=debug renovate shop/shop-api > ../debug-4.log 2>&1
grep -E "^ INFO: PR created|Adding npmrc entry|Spawning npm install" ../debug-4.log \
| sed -E 's/ \(repository=shop\/shop-api, /(/' | cut -c1-88
curl -s -u "$ADMIN" "$R/pulls" \
| jq -r '.[] | "#\(.number) \(.head.ref) \(.title)"' | cut -c1-88Expected:
v1.1.0
+ @shop/[email protected]
sha256:a1ed55b59173…
127.0.0.1:3000/shop/base:1.1.0
DEBUG: Adding npmrc entry for //127.0.0.1:3000/api/packages/ with key _authToken(branch=
INFO: PR created(branch=renovate/127.0.0.1-3000-shop-base-1.x)
DEBUG: Adding npmrc entry for //127.0.0.1:3000/api/packages/ with key _authToken(branch=
DEBUG: Spawning npm install to create ./package-lock.json(branch=renovate/shop-money-1.x
INFO: PR created(branch=renovate/shop-money-1.x)
#3 renovate/shop-money-1.x Update dependency @shop/money to v1.1.0
#2 renovate/127.0.0.1-3000-shop-base-1.x Update 127.0.0.1:3000/shop/base Docker tag to
For the lockfile, Renovate calls npm install. To do so,
it writes the npm hostRules as _authToken into
a temporary .npmrc. Does that end up in the PR?
curl -s -u "$ADMIN" "$R/pulls/3/files" | jq -r '.[].filename'
curl -s -u "$ADMIN" "$R/pulls/3.diff" | grep -E '^[-+] +"(version|resolved)"' \
| cut -c1-88
curl -s -u "$ADMIN" "$R/pulls/2.diff" | grep -E '^[-+]FROM'Expected:
package-lock.json
package.json
- "version": "1.0.0",
- "resolved": "http://127.0.0.1:3000/api/packages/shop/npm/%40shop%2Fmoney/-/1.0.0/
+ "version": "1.1.0",
+ "resolved": "http://127.0.0.1:3000/api/packages/shop/npm/%40shop%2Fmoney/-/1.1.0/
-FROM 127.0.0.1:3000/shop/base:1.0.0
+FROM 127.0.0.1:3000/shop/base:1.1.0
No. The .npmrc in the repo stays unchanged, and the
lockfile points to the private registry. The branch name of the image PR
contains host and port because the package name contains them.
Save your progress? Sign up for free
Drill 7: npmrc and npmrcMerge
The operator can give Renovate a global .npmrc
(npmrc, as the env var RENOVATE_NPMRC), for
example for the scopes of all teams. A team lager gets its
own scope:
export RENOVATE_NPMRC="@lager:registry=$FORGEJO/api/packages/lager/npm/"
renovate shop/shop-api 2>&1 \
| grep -E "npmrc|Failed to look up|Autoclosing|\"prTitle\": \"Update dep" | cut -c1-88
curl -s -u "$ADMIN" "$R/pulls" \
| jq -r '.[] | "#\(.number) \(.head.ref) \(.title)"' | cut -c1-88
LOG_LEVEL=debug renovate --dry-run=lookup shop/shop-api 2>&1 | grep -E "statusCode=" \
| sed -E 's/.*GET ([^ ]+) .*statusCode=(-?[0-9]+).*/\2 \1/'Expected:
INFO: Repo .npmrc file is ignored due to config.npmrc with config.npmrcMerge=false (r
"npmrcFileName": ".npmrc"
"warnings": ["Failed to look up npm package @shop/money: no-result"],
"warnings": ["Failed to look up npm package @shop/money: no-result"],
INFO: Autoclosing PR (repository=shop/shop-api)
"prTitle": "Update dependency @shop/money to v1.1.0"
#2 renovate/127.0.0.1-3000-shop-base-1.x Update 127.0.0.1:3000/shop/base Docker tag to
404 https://registry.npmjs.org/@shop%2Fmoney
Two lessons at once. First, a global npmrc completely
replaces the repo’s .npmrc. Without the scope line,
Renovate asks registry.npmjs.org for
@shop/money. If a package with the same name existed there,
that would be a dependency confusion hole. Second, Renovate closes an
open PR as soon as it no longer finds the update. So an expired token
costs you not only new PRs, but existing ones too.
With npmrcMerge, both files are merged:
export RENOVATE_NPMRC_MERGE=true
renovate shop/shop-api 2>&1 | grep -E "npmrc|Failed to look up|PR created" | cut -c1-88
curl -s -u "$ADMIN" "$R/pulls" \
| jq -r '.[] | "#\(.number) \(.head.ref) \(.title)"' | cut -c1-88
curl -s -u "$ADMIN" "$R/pulls?state=closed" | jq -r '.[] | "#\(.number) \(.title)"'
unset RENOVATE_NPMRC RENOVATE_NPMRC_MERGEExpected:
INFO: PR created (repository=shop/shop-api, branch=renovate/shop-money-1.x)
#4 renovate/shop-money-1.x Update dependency @shop/money to v1.1.0
#2 renovate/127.0.0.1-3000-shop-base-1.x Update 127.0.0.1:3000/shop/base Docker tag to
#3 Update dependency @shop/money to v1.1.0 - autoclosed
The PR comes back, but as a new PR #4. Comments and reviews from #3 stay attached to the closed PR.
Tip: Renovate internally translates an
_authTokeninnpmrcinto ahostRulesrule withhttps://. For the HTTP registry in the lab, that rule does not apply. In production with HTTPS, both work;hostRulesare still the usual way.
Save your progress? Sign up for free
Drill 8: secrets for repo hostRules
Sometimes the repo itself should determine which registry it needs,
for example because only one team uses it. Then the
hostRules live in renovate.json, but instead
of the token there is only a placeholder. Only the global option
secrets knows the value.
unset RENOVATE_HOST_RULES
cp ~/renovate-lab/code/tag08/shop-api/renovate-secrets.json renovate.json
jq '.hostRules' renovate.json
renovate-config-validator --no-global renovate.json >/dev/null
git add -A
git commit -qm "hostRules mit Platzhaltern"
git push -q origin main
renovate shop/shop-api 2>&1 | grep -E "validationMessage|\"result\"" | sort -u \
| cut -c1-88
curl -s -u "$ADMIN" "$R/issues?state=open&type=issues" \
| jq -r '.[] | "#\(.number) \(.title)"'Expected:
[
{
"matchHost": "http://127.0.0.1:3000/api/packages/",
"hostType": "npm",
"token": "{{ secrets.FORGEJO_PACKAGES }}"
},
{
"matchHost": "127.0.0.1",
"hostType": "docker",
"username": "renovate-bot",
"password": "{{ secrets.FORGEJO_PACKAGES }}",
"insecureRegistry": true
}
]
"validationMessage": "The following secrets name was not found in config: FOR
"result": "config-validation",
#5 Action Required: Fix Renovate Configuration
#1 Dependency Dashboard
An unknown name is a configuration error: Renovate creates the issue and stops the repo. The open PRs remain untouched. Now the operator supplies the value:
export RENOVATE_SECRETS=$(jq -nc --arg t "$RENOVATE_TOKEN" '{FORGEJO_PACKAGES: $t}')
LOG_LEVEL=debug renovate shop/shop-api > ../debug-5.log 2>&1
grep -E "authentication for (http|127).*(npm|docker)" ../debug-5.log | cut -c1-88
curl -s -u "$ADMIN" "$R/issues?state=open&type=issues" \
| jq -r '.[] | "#\(.number) \(.title)"'
grep -c "$RENOVATE_TOKEN" ../debug-5.logExpected:
DEBUG: Adding token authentication for http://127.0.0.1:3000/api/packages/ (hostType=npm
DEBUG: Adding password authentication for 127.0.0.1 (hostType=docker) to hostRules (repo
#1 Dependency Dashboard
0
The error issue is closed, and the token does not even appear in the
debug log: Renovate masks every value from secrets as
***. Three protection mechanisms are built in:
secretsis a global option. In a repo config, the validator reports “a global option reserved only for Renovate’s global configuration”.- Renovate refuses placeholders in fields that start with
branch,commit,group,pr, orsemantic. That way the value cannot wander into a PR title. - The repo knows only the name. Anyone who wants to change the value needs access to the global config.
Warning: You will find
encryptedwith the encryption tool fromapp.renovatebot.comin many old guides. The Mend cloud apps no longer read it and also use{{ secrets.NAME }}. Self-hosted, it only works with your ownprivateKeyand a self-hosted tool. Usesecrets.
Save your progress? Sign up for free
Checkpoint
@shop/money is locked anonymously, and the bot reads
version 1.1.0:
cd ~/renovate-lab/tag08
R="$FORGEJO/api/v1/repos/shop/shop-api"
curl -s -o /dev/null -w '%{http_code}\n' "$FORGEJO/api/packages/shop/npm/@shop%2fmoney"
curl -s -H "Authorization: token $RENOVATE_TOKEN" \
"$FORGEJO/api/packages/shop/npm/@shop%2fmoney" | jq -r '.versions | keys[]'Expected:
401
1.0.0
1.1.0
PRs for both internal packages are open:
curl -s -u "$ADMIN" "$R/pulls" | jq -r '.[].head.ref'Expected:
R08_KP
The token appears nowhere in the Git history:
git -C shop-api log -p | grep -cF "$RENOVATE_TOKEN"Expected:
0
Challenge
The org shop becomes private. Prove that
Renovate can then no longer read the packages, even though the bot is a
collaborator of shop-api. Fix that without giving the bot
access to any other repos.
Hint: In a private org, only members see the packages, and a team can grant permissions for the “Packages” unit alone.
Solution
cd ~/renovate-lab/tag08/shop-api
curl -s -u "$ADMIN" -X PATCH -H 'Content-Type: application/json' \
"$FORGEJO/api/v1/orgs/shop" -d '{"visibility":"private"}' | jq -r .visibility
LOG_LEVEL=debug renovate --dry-run=lookup shop/shop-api 2>&1 \
| grep -E "statusCode=" | grep -v /api/v1/ \
| sed -E 's/.*GET ([^ ]+) .*statusCode=(-?[0-9]+).*/\2 \1/'
ID=$(curl -s -u "$ADMIN" -X POST -H 'Content-Type: application/json' \
"$FORGEJO/api/v1/orgs/shop/teams" -d '{"name": "package-reader",
"permission": "read", "includes_all_repositories": false,
"units_map": {"repo.packages": "read"}}' | jq -r .id)
curl -s -o /dev/null -w "%{http_code}\n" -u "$ADMIN" -X PUT \
"$FORGEJO/api/v1/teams/$ID/members/renovate-bot"
renovate shop/shop-api 2>&1 | grep -cE "^ WARN|Autoclosing"
curl -s -u "$ADMIN" "$R/pulls" \
| jq -r '.[] | "#\(.number) \(.head.ref) \(.title)"' | cut -c1-88Expected:
private
401 http://127.0.0.1:3000/api/packages/shop/npm/@shop%2Fmoney
401 http://127.0.0.1:3000/v2/shop/base/tags/list?n=10000
204
0
#4 renovate/shop-money-1.x Update dependency @shop/money to v1.1.0
#2 renovate/127.0.0.1-3000-shop-base-1.x Update 127.0.0.1:3000/shop/base Docker tag to
The dry run shows the error without closing PRs. The team
package-reader grants only read access to packages and
contains no repo. The bot stays as small as possible.
Cleanup for Day 9: log out, delete local images, make the org public
again, clear the env. Day 9 sets up shop-api from scratch
(DELETE and push as on Day 0).
docker logout 127.0.0.1:3000
docker rmi 127.0.0.1:3000/shop/base:1.0.0 127.0.0.1:3000/shop/base:1.1.0 >/dev/null
curl -s -u "$ADMIN" -X PATCH -H 'Content-Type: application/json' \
"$FORGEJO/api/v1/orgs/shop" -d '{"visibility":"public"}' | jq -r .visibility
unset RENOVATE_HOST_RULES RENOVATE_SECRETS REGExpected:
Removing login credentials for 127.0.0.1:3000
public
Save your progress? Sign up for free
Enterprise Note
- Credentials belong in the global config of the Renovate operation
(Day 9), and there in a secret backend, for example as a Kubernetes
Secret for the CronJob (Day 10). In
renovate.jsonthere are at most{{ secrets.NAME }}placeholders. - Give Renovate a dedicated read token per registry (Artifactory, Nexus, Harbor, GitLab/GitHub Packages). Renovate needs write permissions only on the Git platform.
- Registry proxies and mirrors (
registryUrls,registryAliases) need the samehostRules. Test every combination of registry andhostTypeindividually. - Monitor “Package lookup failures” in the JSON logs (Day 14). An expired token silently closes open PRs.
- Plan for
internalHostAccess=block: internal registries then need ahostRulesrule withallowInternal: truein the admin config.