failed start agent pod
- Dominant language
- Go
- Stars
- 2.3k
- Forks
- 303
- PR merge metrics
- No merged PRs in 30d
Description
start agent pod got error log
```
+ grep -q io.containerd.runtime.v1.linux /proc/10281/cmdline
+ exec /usr/bin/nsenter -m/proc/1/ns/mnt -- /usr/bin/lxcfs -p /run/lxcfs-18406.pid /var/lib/lxc/lxcfs/
nsenter: can't execute '/usr/bin/lxcfs': No such file or directory
+ /bin/debug-agent
No config file provided. Using all default values.
2020/10/19 06:33:30 server.go:38: Listening on 0.0.0.0:10027
```
in container, command exec result:
```
/ # ls -al /usr/bin/lxcfs
-rwxr-xr-x 1 root root 22360 Jan 13 2020 /usr/bin/lxcfs
/ # /usr/bin/lxcfs -v
mount namespace: 5
hierarchies:
0: fd: 6: cpuset
1: fd: 7: devices
2: fd: 8: hugetlb
3: fd: 9: memory
4: fd: 10: freezer
5: fd: 11: rdma
6: fd: 12: net_cls,net_prio
7: fd: 13: perf_event
8: fd: 14: blkio
9: fd: 15: pids
10: fd: 16: cpu,cpuacct
11: fd: 17: files
12: fd: 18: name=systemd
13: fd: 19: unified
fuse: missing mountpoint parameter
/ #
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the reported agent-pod startup log and the container checks for /usr/bin/lxcfs and its version output. Trace why nsenter cannot execute lxcfs in the target mount namespace, then verify the agent pod starts without that error; the repository notice says this project is no longer maintained and points to another project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100