Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
K
k3s
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jacklull
k3s
Commits
08cdc0ef
Commit
08cdc0ef
authored
May 31, 2016
by
derekwaynecarr
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix system container detection
parent
60c1ec8e
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
35 additions
and
5 deletions
+35
-5
container_manager_linux.go
pkg/kubelet/cm/container_manager_linux.go
+35
-5
No files found.
pkg/kubelet/cm/container_manager_linux.go
View file @
08cdc0ef
...
@@ -536,19 +536,49 @@ func ensureProcessInContainer(pid int, oomScoreAdj int, manager *fs.Manager) err
...
@@ -536,19 +536,49 @@ func ensureProcessInContainer(pid int, oomScoreAdj int, manager *fs.Manager) err
return
utilerrors
.
NewAggregate
(
errs
)
return
utilerrors
.
NewAggregate
(
errs
)
}
}
// Gets the (CPU) container the specified pid is in.
// getContainer returns the cgroup associated with the specified pid.
// It enforces a unified hierarchy for memory and cpu cgroups.
// On systemd environments, it uses the name=systemd cgroup for the specified pid.
func
getContainer
(
pid
int
)
(
string
,
error
)
{
func
getContainer
(
pid
int
)
(
string
,
error
)
{
cgs
,
err
:=
cgroups
.
ParseCgroupFile
(
fmt
.
Sprintf
(
"/proc/%d/cgroup"
,
pid
))
cgs
,
err
:=
cgroups
.
ParseCgroupFile
(
fmt
.
Sprintf
(
"/proc/%d/cgroup"
,
pid
))
if
err
!=
nil
{
if
err
!=
nil
{
return
""
,
err
return
""
,
err
}
}
cg
,
ok
:=
cgs
[
"cpu"
]
cpu
,
found
:=
cgs
[
"cpu"
]
if
ok
{
if
!
found
{
return
cg
,
nil
return
""
,
cgroups
.
NewNotFoundError
(
"cpu"
)
}
memory
,
found
:=
cgs
[
"memory"
]
if
!
found
{
return
""
,
cgroups
.
NewNotFoundError
(
"memory"
)
}
// since we use this container for accounting, we need to ensure its a unified hierarchy.
if
cpu
!=
memory
{
return
""
,
fmt
.
Errorf
(
"cpu and memory cgroup hierarchy not unified. cpu: %s, memory: %s"
,
cpu
,
memory
)
}
// on systemd, every pid is in a unified cgroup hierarchy (name=systemd as seen in systemd-cgls)
// cpu and memory accounting is off by default, users may choose to enable it per unit or globally.
// users could enable CPU and memory accounting globally via /etc/systemd/system.conf (DefaultCPUAccounting=true DefaultMemoryAccounting=true).
// users could also enable CPU and memory accounting per unit via CPUAccounting=true and MemoryAccounting=true
// we only warn if accounting is not enabled for CPU or memory so as to not break local development flows where kubelet is launched in a terminal.
// for example, the cgroup for the user session will be something like /user.slice/user-X.slice/session-X.scope, but the cpu and memory
// cgroup will be the closest ancestor where accounting is performed (most likely /) on systems that launch docker containers.
// as a result, on those systems, you will not get cpu or memory accounting statistics for kubelet.
// in addition, you would not get memory or cpu accounting for the runtime unless accounting was enabled on its unit (or globally).
if
systemd
,
found
:=
cgs
[
"name=systemd"
];
found
{
if
systemd
!=
cpu
{
glog
.
Warningf
(
"CPUAccounting not enabled for pid: %d"
,
pid
)
}
if
systemd
!=
memory
{
glog
.
Warningf
(
"MemoryAccounting not enabled for pid: %d"
,
pid
)
}
return
systemd
,
nil
}
}
return
""
,
cgroups
.
NewNotFoundError
(
"cpu"
)
return
cpu
,
nil
}
}
// Ensures the system container is created and all non-kernel threads and process 1
// Ensures the system container is created and all non-kernel threads and process 1
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment