-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nomad 1.3.0 - cgroup-parent for systemd error #13022
Comments
Hi @replay111, did you set the value When using the docker driver Nomad needs control over where the cgroup for the container gets created, and I suspect that is going to conflict with the systemd cgroup docker driver. |
@shoenig - yes - it is placed at the top of the issue:
and this is added during the installation (of docker) by my ansible module. |
Hi, I've updated my Ansible Collection and now I do not add this line that reffers to cgroup driver: |
Thanks for the update @replay111. Since this is just a configuration issue I think we should update our |
@shoenig I'm not sure how it's determined but at least Debian 11 (default cgroupv2) / Linux 5.10.0-10-amd64 / docker 5:20.10.16 cgroup driver is systemd. If nomad doesn't work with this driver it should be mentioned that native.cgroupdriver=cgroupfs should be configured, not unset:
|
Found, It's from 20.10.0 https://docs.docker.com/engine/release-notes/#20100
|
@valodzka I'm not sure #40846 is the full story; in practice I think leaving the driver blank in turn enables setting a custom cgroup parent and setting it to systemd forces the systemd hierarchy. Could be totally wrong; docker is frankly an enigma. In reality what Nomad really needs is to be able to just set the cgroup path the docker container should use. Unfortunately moby/moby#43363 seems to have been ignored. |
Encountered this same issue when upgrading to 1.3.1. We are running RHEL's supported version of docker, which is configured to use the systemd cgroup driver. Considering moving back to 1.2.8, until this issue is resolved. Will the systemd cgroup driver be supported? |
@jacksod1 can you (or someone) describe (or link to docs) what needs to be done to support this configuration? |
Should be fixed as of #18371 (Nomad 1.7) |
Nomad version
nomad version
Nomad v1.3.0 (52e95d6)
Operating system and Environment details
cat /etc/*release
Oracle Linux Server release 8.5
NAME="Oracle Linux Server"
VERSION="8.5"
ID="ol"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="8.5"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Oracle Linux Server 8.5"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:oracle:linux:8:5:server"
HOME_URL="https://linux.oracle.com/"
BUG_REPORT_URL="https://bugzilla.oracle.com/"
ORACLE_BUGZILLA_PRODUCT="Oracle Linux 8"
ORACLE_BUGZILLA_PRODUCT_VERSION=8.5
ORACLE_SUPPORT_PRODUCT="Oracle Linux"
ORACLE_SUPPORT_PRODUCT_VERSION=8.5
Red Hat Enterprise Linux release 8.5 (Ootpa)
Oracle Linux Server release 8.5
docker version
Client: Docker Engine - Community
Version: 20.10.16
API version: 1.41
Go version: go1.17.10
Git commit: aa7e414
Built: Thu May 12 09:17:20 2022
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.16
API version: 1.41 (minimum version 1.12)
Go version: go1.17.10
Git commit: f756502
Built: Thu May 12 09:15:41 2022
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.4
GitCommit: 212e8b6fa2f44b9c21b2798135fc6fb7c53efc16
runc:
Version: 1.1.1
GitCommit: v1.1.1-0-g52de29d
docker-init:
Version: 0.19.0
GitCommit: de40ad0
cat /etc/docker/daemon.json
{
"exec-opts": ["native.cgroupdriver=systemd"],
"metrics-addr" : "0.0.0.0:9323",
"insecure-registries": [
"172.30.0.0/16"
]
}
Issue
Job is failing with error:
Reproduction steps
Nomad job definition:
Expected Result
Container with Jenkins up and running - no more errors like mentioned at the top
Actual Result
For now as mentioned:
Job file (if appropriate)
Nomad Server logs (if appropriate)
Nomad Client logs (if appropriate)
Nomad server and client are on the same host - test configuration
NOTE
Exactly same configuration but with Nomad 1.2.6 (I stopped service removed everything deployed instance with 1.2.6) works without any problems.
The text was updated successfully, but these errors were encountered: