GoogleContainerTools/skaffold
GitHub で見るSkaffold & local docker daemon registry mirror
Open
#7,368 opened on 2022年5月3日
bugbash/q4-2022help wantedkind/bugkind/frictionpriority/awaiting-more-evidence
説明
Expected behavior
- Skaffold should build images without hitting docker pull rate limits.
Actual behavior
- servicename: Error checking cache. getting hash for artifact "servicename": getting dependencies for "servicename": parsing ONBUILD instructions: retrieving image "php:8.0-apache": GET https://index.docker.io/v2/library/php/manifests/8.0-apache: TOOMANYREQUESTS: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
Information
- Skaffold version: v1.35.2
- Operating system: Ubuntu 20.04
- Installed via: --> direct install via website ( For Linux x86_64 (amd64) )
- Output of skaffold config list: -- kube-context: [my AWS EKS cluster] -- default-repo: [my private docker repo] -- local-cluster: false
- Contents of skaffold.yaml:
<paste your skaffold.yaml here>
# Copyright 2021 Google LLC
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
apiVersion: skaffold/v2beta26
kind: Config
build:
local:
concurrency: 8
tryImportMissing: true
artifacts:
# image tags are relative; to specify an image repo (e.g. GCR), you
# must provide a "default repo" using one of the methods described
# here:
# https://skaffold.dev/docs/concepts/#image-repository-handling
- image: servicename
context: src/servicename
tagPolicy:
gitCommit: {}
deploy:
kubectl:
manifests:
- ./kubernetes-manifests/**.yaml
Steps to reproduce the behavior
- In my local docker daemon, I have defined a registry mirror.
- Skaffold fails to build the application as it cannot pull "python:3.7-slim" or other images.
- However if I run docker pull python:3.7-slim, it uses my registry mirror and pulls it from there.
- My skaffold is configured to use the local docker daemon. Why is this error appearing with skaffold when docker pull, pulls the image successfully?
- Does skaffold ignore the docker daemon settings or is it trying to build on my EKS cluster?