Comments (8)
查看target Pod状态为PodFitsHostPorts
kubectl describe pod日志
Status: Failed
Reason: PodFitsHostPorts
Message: Pod Predicate PodFitsHostPorts failed
from kubectl-debug.
The problem is that the forked pod ran to COMPLETE status instead of RUNNING.
How many containers in the target Pod?
from kubectl-debug.
查看target Pod状态为PodFitsHostPorts
kubectl describe pod日志
Status: Failed
Reason: PodFitsHostPorts
Message: Pod Predicate PodFitsHostPorts failed
That make sense:
- The original pod (target pod) uses the host network, so does the forked pod;
- The forked pod is explicitly assigned to the same node of original pod in favor of environment consistency;
- The forked pod cannot run in the target node due to the collision of host port.
from kubectl-debug.
The problem is that the forked pod ran to COMPLETE status instead of RUNNING.
How many containers in the target Pod?
The problem is that the pod state of CrashLoopBackOff is definitely not possible to Running。
Our goal is not to find the reason for the CrashLoopBackOff state?
from kubectl-debug.
@kerven88
Yes, of course the goal is to find the reason of the CrashLoopBackOff state.
However, the strategy kubectl-debug
take is to fork a Pod and reproduce the issue in the new Pod. The command
of the new Pod will be replaced so the new Pod won't crash on start. This works in some scenarios but fails for specific scenarios like this.
As for this issue, the problems of the new Pod and the old Pod (target Pod) are actually different:
- The old Pod crash for some reason on start, where we want to find the reason;
- The new Pod cannot run in the target host because the host port has been used by the old Pod, so we cannot proceed on to reproduce the crash at the start time;
HostNetwork
should be special case and kubectl-debug
should have change the port of new Pod.
from kubectl-debug.
@kerven88
Yes, of course the goal is to find the reason of the CrashLoopBackOff state.However, the strategy
kubectl-debug
take is to fork a Pod and reproduce the issue in the new Pod. Thecommand
of the new Pod will be replaced so the new Pod won't crash on start. This works in some scenarios but fails for specific scenarios like this.As for this issue, the problems of the new Pod and the old Pod (target Pod) are actually different:
- The old Pod crash for some reason on start, where we want to find the reason;
- The new Pod cannot run in the target host because the host port has been used by the old Pod, so we cannot proceed on to reproduce the crash at the start time;
HostNetwork
should be special case andkubectl-debug
should have change the port of new Pod.
That's right, how can I customize the port number of the new Pod?
from kubectl-debug.
@kerven88 This requires modification of code, hopefully I will submit a PR this weekend, or I can give some guidance if you are willing to work on this.
from kubectl-debug.
@kerven88 This requires modification of code, hopefully I will submit a PR this weekend, or I can give some guidance if you are willing to work on this.
Tks! Looking forward to your PR submitsion。
from kubectl-debug.
Related Issues (20)
- Plugin stuck creating exec stream
- plan to support sts
- Error: No such image HOT 2
- Error: No such image: nicolaka/netshoot:latest HOT 18
- The default agent image version should be coordinated with the plugin
- Do not use HostPort when using --port-forward
- Agent pod failed HOT 4
- not output command result when excute no interactive command
- `RegistrySecretName` inf config file don't work HOT 2
- Errors with containerd runtime HOT 2
- cannot get the debug docker image No such image: docker.io/nicolaka/netshoot:latest HOT 2
- I can't join some pods HOT 1
- k8s.io/api/admissionregistration/v1alpha1: module k8s.io/api@latest found (v0.20.5), but does not contain package k8s.io/api/admissionregistration/v1alpha1 HOT 1
- aliyun-exporter使用时出现错误
- If my target pod has multiple contianers? HOT 1
- Seems the kubectl has build-in debug sub command, it conflicts with it HOT 2
- What is the reason behind `CGO_ENABLED=0`?
- parse namespace error HOT 1
- 项目是结束维护了么,好久没看到更新 HOT 2
- run error when use containerd runtime
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kubectl-debug.