![]() ![]() Operating System: Debian GNU/Linux 9 (stretch) Telling Docker only to build the image, from its dedicated directory where stands the Dockerfile, fails with following output: Step 2/7 : RUN set -x & yum update -y & yum install -y sudo python openssh-server vim & useradd vagrant -create-home -user-group & service sshd start Stdout: Sending build context to Docker daemon 7.68kB Stderr: The command '/bin/sh -c set -x & yum update -y & yum install -y sudo python openssh-server vim & useradd vagrant -create-home -user-group & service sshd start' returned a non-zero code: 139 The command run along with the output from the command is shownĬommand: => default: Building the container from a Dockerfile.ĭefault: Sending build context to Docker daemon 7.68kBĭefault: Step 2/7 : RUN set -x & yum update -y & yum install -y sudo python openssh-server vim & useradd vagrant -create-home -user-group & service sshd startĭefault: The command '/bin/sh -c set -x & yum update -y & yum install -y sudo python openssh-server vim & useradd vagrant -create-home -user-group & service sshd start' returned a non-zero code: 139Ī Docker command executed by Vagrant didn't complete successfully! yum-plugin-ovl is installed on centos:6.x image.īringing machine 'default' up with 'docker' provider.Previous working version of Linux was (uname -a):.Backporting Docker to 17.03 version did not solve the issue.The expected and previous behavior works if I run previous Linux kernel image.Vagrant from Debian repos, at current version in testing: 1.9.1. ![]() ID: YYBN:LCRS:YXZ2:CG3G:N2IQ:EDHI:2HKM:L7EJ:5R3A:LNMP:LRUD:ASUGĪdditional environment details (AWS, VirtualBox, physical, etc.) Operating System: Debian GNU/Linux buster/sid Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslogĬontainerd version: cfb82a876ecc11b5ca0977d1733adbe58599088a Network: bridge host macvlan null overlay Here's a minimal Dockerfile for which error occured:. ![]() Also, using direct images from (instead of building our own images from them) with docker run -t -i /bin/bash fails to give user a shell. ![]() This error is also reported in case of use of sole Dockerfile, with docker build. Using 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 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). #47?ĭocker 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |