GoogleContainerTools/skaffold

skaffold dev can not match manifest ./infra/k8s/* file

Open

#6,701 opened on Oct 7, 2021

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (12,822 stars) (1,416 forks)batch import
bugbash/q4-2022help wantedkind/bugpriority/awaiting-more-evidencepriority/p3

Description

my code.

apiVersion: skaffold/v2alpha3
kind: Config
deploy:
  kubectl:
    manifests: 
      - ./infra/k8s/*
build:
  local: 
    push: false
  artifacts:
    - image: lekan123/auth
      context: auth
      docker:
        dockerfile: Dockerfile
      sync:
        manual: 
          - src: 'src/**/*.ts'
            dest: .

console log

Listing files to watch...
 - lekan123/auth
Generating tags...
 - lekan123/auth -> lekan123/auth:a9978a8
Checking cache...
 - lekan123/auth: Found Locally
Tags used in deployment:
 - lekan123/auth -> lekan123/auth:199adcc986f977ea49a21d8c12a86c65f16d85e40c6003fdef976efbe2d17bbb
Starting deploy...
 - deployment.apps/auth-depl configured
 - service/auth-svr configured
Waiting for deployments to stabilize...
 - deployment/auth-depl is ready.
Deployments stabilized in 2.079 seconds
Press Ctrl+C to exit
WARN[0002] ./infra/k8s/* did not match any file          subtask=-1 task=DevLoop
Watching for changes...
[auth] 
[auth] > auth@1.0.0 start
[auth] > ts-node-dev src/index.ts
[auth] 
[auth] [INFO] 09:11:00 ts-node-dev ver. 1.1.8 (using ts-node ver. 9.1.1, typescript ver. 4.4.3)
[auth] Auth running on port: 3000
WARN[0003] ./infra/k8s/* did not match any file          subtask=-1 task=DevLoop
Generating tags...
 - lekan123/auth -> lekan123/auth:latest
Some taggers failed. Rerun with -vdebug for errors.
Checking cache...
 - lekan123/auth: Found Locally
Tags used in deployment:
 - lekan123/auth -> lekan123/auth:c0721c1b37822eb7bae5384375f52d33a962650446438a6e71997893fbdeab92
Starting deploy...
WARN[0003] ./infra/k8s/* did not match any file          subtask=-1 task=DevLoop
Waiting for deployments to stabilize...
 - deployment/auth-depl: starting command /usr/local/bin/kubectl --context docker-desktop rollout status deployment auth-depl --namespace default --watch=false: pipe: too many open files
 - deployment/auth-depl failed. Error: starting command /usr/local/bin/kubectl --context docker-desktop rollout status deployment auth-depl --namespace default --watch=false: pipe: too many open files.
WARN[0004] Skipping deploy due to error:1/1 deployment(s) failed  subtask=-1 task=DevLoop
Watching for changes...
WARN[0004] ./infra/k8s/* did not match any file          subtask=-1 task=DevLoop
WARN[0005] ./infra/k8s/* did not match any file          subtask=-1 task=DevLoop
WARN[0006] ./infra/k8s/* did not match any file          subtask=-1 task=DevLoop
WARN[0007] ./infra/k8s/* did not match any file          subtask=-1 task=DevLoop
WARN[0008] ./infra/k8s/* did not match any file          subtask=-1 task=DevLoop
WARN[0009] ./infra/k8s/* did not match any file          subtask=-1 task=DevLoop
WARN[0010] ./infra/k8s/* did not match any file          subtask=-1 task=DevLoop
WARN[0011] ./infra/k8s/* did not match any file          subtask=-1 task=DevLoop
WARN[0012] ./infra/k8s/* did not match any file          subtask=-1 task=DevLoop
^CCleaning up...
WARN[0013] ./infra/k8s/* did not match any file          subtask=-1 task=DevLoop
WARN[0013] deployer cleanup:kubectl delete: pipe: too many open files  subtask=-1 task=DevLoop

Contributor guide

Tech stack
godockerkubernetes
Domain
devops
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of skaffoldKubernetes manifest structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate why the glob pattern `./infra/k8s/*` fails to match files in skaffold's deploy step. Check the file resolution logic in the deploy/kubectl package, specifically the function that expands manifest paths. Reproduce the issue locally with a minimal skaffold config and directory structure. Consider if the path is relative to the skaffold config file location. Look at any existing issues or PRs related to glob matching.
skaffold dev can not match manifest ./infra/k8s/* file · GoogleContainerTools/skaffold#6701 | Good First Issue