Hi Ian,
Thanks for your attention to this.
I just tried out the following combinations:
Linux Kernel v4.7:
vsyscall=emulate
vsyscall=native
vsyscall=none
Linux Kernel v4.8
vsyscall=emulate
vsyscall=native
vsyscall=none
The commands work every time, except when vsyscall=none is set, for
both ker
On Tue, 2016-11-22 at 12:17 +, Ian Campbell wrote:
> On Sun, 2016-11-20 at 09:57 +, Luís Picciochi Oliveira wrote:
> >
> > While using Docker, some commands on some images stopped working.
> > For
> > example:
> >
> > $ docker run -it --rm centos:centos6 bash
> > This does not work. It
On Sun, 2016-11-20 at 09:57 +, Luís Picciochi Oliveira wrote:
> While using Docker, some commands on some images stopped working. For
> example:
>
> $ docker run -it --rm centos:centos6 bash
> This does not work. It always returns with code 139:
>
> $ echo $?
> 139
FYI something similar
20 November 2016 at 01:57, Luís Picciochi Oliveira wrote:
> While using Docker, some commands on some images stopped working. For example:
>
> $ docker run -it --rm centos:centos6 bash
> This does not work. It always returns with code 139:
>
> $ echo $?
> 139
>
>
> ...but the following does
Package: docker.io
Version: 1.11.2~ds1-6
Severity: important
Dear Maintainer,
While using Docker, some commands on some images stopped working. For example:
$ docker run -it --rm centos:centos6 bash
This does not work. It always returns with code 139:
$ echo $?
139
...but the following
5 matches
Mail list logo
