{"action":"created","issue":{"url":"https://api.github.com/repos/docker/for-linux/issues/58","repository_url":"https://api.github.com/repos/docker/for-linux","labels_url":"https://api.github.com/repos/docker/for-linux/issues/58/labels{/name}","comments_url":"https://api.github.com/repos/docker/for-linux/issues/58/comments","events_url":"https://api.github.com/repos/docker/for-linux/issues/58/events","html_url":"https://github.com/docker/for-linux/issues/58","id":242038335,"number":58,"title":"Normal running now fails, for CentOS 6.x images, on Debian testing, after upgrading Linux kernel from 4.9 to 4.11","user":{"login":"vincent-ferotin","id":3097321,"avatar_url":"https://avatars6.githubusercontent.com/u/3097321?v=4","gravatar_id":"","url":"https://api.github.com/users/vincent-ferotin","html_url":"https://github.com/vincent-ferotin","followers_url":"https://api.github.com/users/vincent-ferotin/followers","following_url":"https://api.github.com/users/vincent-ferotin/following{/other_user}","gists_url":"https://api.github.com/users/vincent-ferotin/gists{/gist_id}","starred_url":"https://api.github.com/users/vincent-ferotin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vincent-ferotin/subscriptions","organizations_url":"https://api.github.com/users/vincent-ferotin/orgs","repos_url":"https://api.github.com/users/vincent-ferotin/repos","events_url":"https://api.github.com/users/vincent-ferotin/events{/privacy}","received_events_url":"https://api.github.com/users/vincent-ferotin/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":21,"created_at":"2017-07-11T12:59:20Z","updated_at":"2017-07-15T09:16:32Z","closed_at":"2017-07-15T01:02:20Z","body":"<!--\r\nThis issue tracker is for *bug reports* and *feature requests*.\r\nFor questions, and getting help on using docker:\r\n\r\n- Docker documentation - https://docs.docker.com\r\n- Docker Forums - https://forums.docker.com\r\n- Docker community Slack - https://dockercommunity.slack.com/ (register here: http://dockr.ly/community)\r\n- Post a question on StackOverflow, using the Docker tag\r\n-->\r\n\r\n* [x] This is a bug report\r\n* [ ] This is a feature request\r\n* [x] I searched existing issues before opening this one, possibly related to #49, #47?\r\n\r\n<!--\r\nDO NOT report security issues publicly! If you suspect you discovered\r\na security issue, send your report privately to security@docker.com.\r\n-->\r\n\r\n### Expected behavior\r\n\r\ndocker CE 17.06 should work same, for CentoS **6.x** images, with 4.9 or 4.11 Linux kernel version, at `vagrant up`, `docker build .` or `docker run -t -i <image> /bin/bash`. This failure is encountered only with 6.x branch of CentOS, and 4.11 branch of Linux together (it works fine with kernel at 4.9, or kernel at 4.11 with 7.x branch of CentOS).\r\n\r\n### Actual behavior\r\n\r\nUsing Docker through Vagrant, after updating distribution (Debian testing, today), for a CentOS 6.9 image, the latter now returns following error: `default: The command '/bin/sh -c set -x  && yum update -y [...] ' returned a non-zero code: 139`. This error is also reported in case of use of sole Dockerfile, with `docker build .`. Also, using direct images from https://hub.docker.com/_/centos/ (instead of building our own images from them) with `docker run -t -i <image> /bin/bash` fails to give user a shell.\r\n\r\n### Steps to reproduce the behavior\r\n\r\n<!--\r\nDescribe the exact steps to reproduce. If possible, provide a *minimum*\r\nreproduction example; take into account that others do not have access\r\nto your private images, source code, and environment.\r\n\r\nREMOVE SENSITIVE DATA BEFORE POSTING (replace those parts with \"REDACTED\")\r\n-->\r\n\r\n* Here's a minimal Dockerfile for which error occured:\r\n  ```\r\n  FROM centos:6.9\r\n  \r\n  RUN yum update -y\r\n\r\n  CMD [\"/bin/bash\"]\r\n  ```\r\n  `vagrant up` and `docker build .` fail with error:\r\n  ```\r\n  The command '/bin/sh -c yum update -y' returned a non-zero code: 139\r\n  ```\r\n* A more minimal example would be:\r\n  ```\r\n  docker run -t -i centos:6.9 /bin/bash\r\n  ```\r\n  does **not** give user a shell inside the container.\r\n\r\n**Output of `docker version`:**\r\n\r\n```\r\nClient:\r\n Version:      17.06.0-ce\r\n API version:  1.30\r\n Go version:   go1.8.3\r\n Git commit:   02c1d87\r\n Built:        Fri Jun 23 21:17:22 2017\r\n OS/Arch:      linux/amd64\r\n\r\nServer:\r\n Version:      17.06.0-ce\r\n API version:  1.30 (minimum version 1.12)\r\n Go version:   go1.8.3\r\n Git commit:   02c1d87\r\n Built:        Fri Jun 23 21:16:12 2017\r\n OS/Arch:      linux/amd64\r\n Experimental: false\r\n```\r\n\r\n**Output of `docker info`:**\r\n\r\n```\r\nContainers: 14\r\n Running: 0\r\n Paused: 0\r\n Stopped: 14\r\nImages: 27\r\nServer Version: 17.06.0-ce\r\nStorage Driver: overlay2\r\n Backing Filesystem: extfs\r\n Supports d_type: true\r\n Native Overlay Diff: true\r\nLogging Driver: json-file\r\nCgroup Driver: cgroupfs\r\nPlugins: \r\n Volume: local\r\n Network: bridge host macvlan null overlay\r\n Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog\r\nSwarm: inactive\r\nRuntimes: runc\r\nDefault Runtime: runc\r\nInit Binary: docker-init\r\ncontainerd version: cfb82a876ecc11b5ca0977d1733adbe58599088a\r\nrunc version: 2d41c047c83e09a6d61d464906feb2a2f3c52aa4\r\ninit version: 949e6fa\r\nSecurity Options:\r\n seccomp\r\n  Profile: default\r\nKernel Version: 4.11.0-1-amd64\r\nOperating System: Debian GNU/Linux buster/sid\r\nOSType: linux\r\nArchitecture: x86_64\r\nCPUs: 8\r\nTotal Memory: 15.54GiB\r\nName: Tryscoped\r\nID: YYBN:LCRS:YXZ2:CG3G:N2IQ:EDHI:2HKM:L7EJ:5R3A:LNMP:LRUD:ASUG\r\nDocker Root Dir: /var/lib/docker\r\nDebug Mode (client): false\r\nDebug Mode (server): false\r\nRegistry: https://index.docker.io/v1/\r\nExperimental: false\r\nInsecure Registries:\r\n 127.0.0.0/8\r\nLive Restore Enabled: false\r\n\r\nWARNING: No swap limit support\r\n```\r\n\r\n**Additional environment details (AWS, VirtualBox, physical, etc.)**\r\n\r\n* Vagrant from Debian repos, at current version in testing: 1.9.1.\r\n* The expected and previous behavior works if I run previous Linux kernel image.\r\n* Output of uname for failing kernel is:\r\n  ```Linux hostname 4.11.0-1-amd64 #1 SMP Debian 4.11.6-1 (2017-06-19) x86_64 GNU/Linux```\r\n* Backporting Docker to 17.03 version did not solve the issue.\r\n* Previous working version of Linux was (uname -a):\r\n  `Linux hostname 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26) x86_64 GNU/Linux\r\n`\r\n* `yum-plugin-ovl` is installed on centos:6.x image."},"comment":{"url":"https://api.github.com/repos/docker/for-linux/issues/comments/315521640","html_url":"https://github.com/docker/for-linux/issues/58#issuecomment-315521640","issue_url":"https://api.github.com/repos/docker/for-linux/issues/58","id":315521640,"user":{"login":"vincent-ferotin","id":3097321,"avatar_url":"https://avatars6.githubusercontent.com/u/3097321?v=4","gravatar_id":"","url":"https://api.github.com/users/vincent-ferotin","html_url":"https://github.com/vincent-ferotin","followers_url":"https://api.github.com/users/vincent-ferotin/followers","following_url":"https://api.github.com/users/vincent-ferotin/following{/other_user}","gists_url":"https://api.github.com/users/vincent-ferotin/gists{/gist_id}","starred_url":"https://api.github.com/users/vincent-ferotin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vincent-ferotin/subscriptions","organizations_url":"https://api.github.com/users/vincent-ferotin/orgs","repos_url":"https://api.github.com/users/vincent-ferotin/repos","events_url":"https://api.github.com/users/vincent-ferotin/events{/privacy}","received_events_url":"https://api.github.com/users/vincent-ferotin/received_events","type":"User","site_admin":false},"created_at":"2017-07-15T09:16:32Z","updated_at":"2017-07-15T09:16:32Z","body":"Just to be sure to fully understand, which behavior does additional check in `check_config.sh` introduce? In fine, does Docker will run out-of-the-box for Linux Kernel 4.11 with Centos 6.x images, or the configuration of the kernel pointed by _justincormack_ will be needed -- forever?"}}
{"actor":{"display_login":"vincent-ferotin"}}