kubesphere / kubesphere/ks-devops
Image builder Source to Image: Publish an App without a Dockerfile
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 164
- Forks
- 140
- PR merge metrics
- No merged PRs in 30d
Description
k8s version:1.20.10
Kubesphere version:3.1.1
harbor:2.0


An error occurred after creating the submission
InternalError
Internal error occurred: failed calling webhook “s2ibuilder.kb.io”: Post “https://webhook-server-service.kubesphere-devops-system.svc:443/mutate-devops-kubesphere-io-v1alpha1-s2ibuilder?timeout=30s”: dial tcp 10.102.136.136:443: connect: connection refused
pod错误信息Events:
Type Reason Age From Message
Normal Scheduled 45s default-scheduler Successfully assigned devops/f-v1-548d6c6959-rkb6p to master1
Normal Pulling 45s kubelet Pulling image “common/speeder-mgr:latest”
Warning Failed 9s kubelet Failed to pull image “common/speeder-mgr:latest”: rpc error: code = Unknown desc = Error response from daemon: pull access denied for common/speeder-mgr, repository does not exist or may require ‘docker login’: denied: requested access to the resource is denied
Warning Failed 9s kubelet Error: ErrImagePull
Normal BackOff 9s kubelet Back-off pulling image “common/speeder-mgr:latest”
Warning Failed 9s kubelet Error: ImagePullBackOff
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files or tests are named; start by reproducing the Source to Image submission on Kubernetes 1.20.10 with Kubesphere 3.1.1 and inspect the s2ibuilder webhook and pod events. Done means publishing the app without a Dockerfile completes without the webhook connection refusal or ImagePullBackOff errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100