Running a CentOS Docker Image on Arch Linux exits with code 139?
up vote
0
down vote
favorite
I am trying to run a CentOS Docker Image on my Arch Linux host. Running the following command returns nothing except the 139 error code:
$ docker run -ti centos:centos6 /bin/bash
[139] $
I have the CentOS Docker image:
centos centos6 0cbf37812bff 2 weeks ago 194MB
and a centOS container is there under the list of containers
$ docker ps -a|grep cento
2ef0f0d7439c centos:centos6 "/bin/bash" 5 minutes ago Exited (139) 5 minutes ago elated_turing
Docker logs also returns nothing:
$ docker logs <container id>
$
I have tried using other Docker images and they work, it only seems to affect the CentOS image but I need to use centOS for my work.
centos arch-linux docker
asked Oct 29 at 9:41
Thomas Crowley
135
|
show 1 more comment
up vote
0
down vote
favorite
I am trying to run a CentOS Docker Image on my Arch Linux host. Running the following command returns nothing except the 139 error code:
$ docker run -ti centos:centos6 /bin/bash
[139] $
I have the CentOS Docker image:
centos centos6 0cbf37812bff 2 weeks ago 194MB
and a centOS container is there under the list of containers
$ docker ps -a|grep cento
2ef0f0d7439c centos:centos6 "/bin/bash" 5 minutes ago Exited (139) 5 minutes ago elated_turing
Docker logs also returns nothing:
$ docker logs <container id>
$
I have tried using other Docker images and they work, it only seems to affect the CentOS image but I need to use centOS for my work.
centos arch-linux docker
asked Oct 29 at 9:41
Thomas Crowley
135
What doesdocker logs <container>show?
– slm♦
Oct 29 at 11:55
@slm nothing is returned
– Thomas Crowley
Oct 29 at 12:18
Can you try removing the container and then removing the image and re-downloading it again?
– slm♦
Oct 29 at 12:36
Also make sure SELinux is enabled - bugzilla.redhat.com/show_bug.cgi?id=1488516.
– slm♦
Oct 29 at 12:38
@slm SELinux isn't fully supported with Arch, and the installation process includes about 100 steps, so are you sure this will solve it? wiki.archlinux.org/index.php/…
– Thomas Crowley
Oct 29 at 14:44
|
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am trying to run a CentOS Docker Image on my Arch Linux host. Running the following command returns nothing except the 139 error code:
$ docker run -ti centos:centos6 /bin/bash
[139] $
I have the CentOS Docker image:
centos centos6 0cbf37812bff 2 weeks ago 194MB
and a centOS container is there under the list of containers
$ docker ps -a|grep cento
2ef0f0d7439c centos:centos6 "/bin/bash" 5 minutes ago Exited (139) 5 minutes ago elated_turing
Docker logs also returns nothing:
$ docker logs <container id>
$
I have tried using other Docker images and they work, it only seems to affect the CentOS image but I need to use centOS for my work.
centos arch-linux docker
asked Oct 29 at 9:41
Thomas Crowley
135
I am trying to run a CentOS Docker Image on my Arch Linux host. Running the following command returns nothing except the 139 error code:
$ docker run -ti centos:centos6 /bin/bash
[139] $
I have the CentOS Docker image:
centos centos6 0cbf37812bff 2 weeks ago 194MB
and a centOS container is there under the list of containers
$ docker ps -a|grep cento
2ef0f0d7439c centos:centos6 "/bin/bash" 5 minutes ago Exited (139) 5 minutes ago elated_turing
Docker logs also returns nothing:
$ docker logs <container id>
$
I have tried using other Docker images and they work, it only seems to affect the CentOS image but I need to use centOS for my work.
centos arch-linux docker
centos arch-linux docker
asked Oct 29 at 9:41
Thomas Crowley
135
asked Oct 29 at 9:41
Thomas Crowley
135
edited Oct 29 at 12:17
asked Oct 29 at 9:41
Thomas Crowley
135
asked Oct 29 at 9:41
Thomas Crowley
135
asked Oct 29 at 9:41
Thomas Crowley
135
135
What doesdocker logs <container>show?
– slm♦
Oct 29 at 11:55
@slm nothing is returned
– Thomas Crowley
Oct 29 at 12:18
Can you try removing the container and then removing the image and re-downloading it again?
– slm♦
Oct 29 at 12:36
Also make sure SELinux is enabled - bugzilla.redhat.com/show_bug.cgi?id=1488516.
– slm♦
Oct 29 at 12:38
@slm SELinux isn't fully supported with Arch, and the installation process includes about 100 steps, so are you sure this will solve it? wiki.archlinux.org/index.php/…
– Thomas Crowley
Oct 29 at 14:44
|
show 1 more comment
What doesdocker logs <container>show?
– slm♦
Oct 29 at 11:55
@slm nothing is returned
– Thomas Crowley
Oct 29 at 12:18
Can you try removing the container and then removing the image and re-downloading it again?
– slm♦
Oct 29 at 12:36
Also make sure SELinux is enabled - bugzilla.redhat.com/show_bug.cgi?id=1488516.
– slm♦
Oct 29 at 12:38
@slm SELinux isn't fully supported with Arch, and the installation process includes about 100 steps, so are you sure this will solve it? wiki.archlinux.org/index.php/…
– Thomas Crowley
Oct 29 at 14:44
What does
docker logs <container> show?– slm♦
Oct 29 at 11:55
What does
docker logs <container> show?– slm♦
Oct 29 at 11:55
@slm nothing is returned
– Thomas Crowley
Oct 29 at 12:18
@slm nothing is returned
– Thomas Crowley
Oct 29 at 12:18
Can you try removing the container and then removing the image and re-downloading it again?
– slm♦
Oct 29 at 12:36
Can you try removing the container and then removing the image and re-downloading it again?
– slm♦
Oct 29 at 12:36
Also make sure SELinux is enabled - bugzilla.redhat.com/show_bug.cgi?id=1488516.
– slm♦
Oct 29 at 12:38
Also make sure SELinux is enabled - bugzilla.redhat.com/show_bug.cgi?id=1488516.
– slm♦
Oct 29 at 12:38
@slm SELinux isn't fully supported with Arch, and the installation process includes about 100 steps, so are you sure this will solve it? wiki.archlinux.org/index.php/…
– Thomas Crowley
Oct 29 at 14:44
@slm SELinux isn't fully supported with Arch, and the installation process includes about 100 steps, so are you sure this will solve it? wiki.archlinux.org/index.php/…
– Thomas Crowley
Oct 29 at 14:44
|
show 1 more comment
1 Answer
1
active
oldest
votes
up vote
0
down vote
They were changes made on vsyscall linking in the Linux Kernel, starting with version 4.11, that caused issues with containers running Centos 6.x
2 solutions :
- Use a 7.x Centos image
- Try to boot the kernel with the parameter
vsyscall=emulate
Example with GRUB, modify /etc/default/grub :
GRUB_CMDLINE_LINUX_DEFAULT="vsyscall=emulate"
And then run update-grub
Example with systemd-boot, modify your conf in /boot/loader/entries and add the parameter to the options line :
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options *EXISTINGPARAMS* vsyscall=emulate
answered yesterday
ldclrcq
11
New contributor
ldclrcq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f478387%2frunning-a-centos-docker-image-on-arch-linux-exits-with-code-139%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
They were changes made on vsyscall linking in the Linux Kernel, starting with version 4.11, that caused issues with containers running Centos 6.x
2 solutions :
- Use a 7.x Centos image
- Try to boot the kernel with the parameter
vsyscall=emulate
Example with GRUB, modify /etc/default/grub :
GRUB_CMDLINE_LINUX_DEFAULT="vsyscall=emulate"
And then run update-grub
Example with systemd-boot, modify your conf in /boot/loader/entries and add the parameter to the options line :
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options *EXISTINGPARAMS* vsyscall=emulate
answered yesterday
ldclrcq
11
New contributor
ldclrcq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
They were changes made on vsyscall linking in the Linux Kernel, starting with version 4.11, that caused issues with containers running Centos 6.x
2 solutions :
- Use a 7.x Centos image
- Try to boot the kernel with the parameter
vsyscall=emulate
Example with GRUB, modify /etc/default/grub :
GRUB_CMDLINE_LINUX_DEFAULT="vsyscall=emulate"
And then run update-grub
Example with systemd-boot, modify your conf in /boot/loader/entries and add the parameter to the options line :
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options *EXISTINGPARAMS* vsyscall=emulate
answered yesterday
ldclrcq
11
New contributor
ldclrcq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
up vote
0
down vote
They were changes made on vsyscall linking in the Linux Kernel, starting with version 4.11, that caused issues with containers running Centos 6.x
2 solutions :
- Use a 7.x Centos image
- Try to boot the kernel with the parameter
vsyscall=emulate
Example with GRUB, modify /etc/default/grub :
GRUB_CMDLINE_LINUX_DEFAULT="vsyscall=emulate"
And then run update-grub
Example with systemd-boot, modify your conf in /boot/loader/entries and add the parameter to the options line :
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options *EXISTINGPARAMS* vsyscall=emulate
answered yesterday
ldclrcq
11
New contributor
ldclrcq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
They were changes made on vsyscall linking in the Linux Kernel, starting with version 4.11, that caused issues with containers running Centos 6.x
2 solutions :
- Use a 7.x Centos image
- Try to boot the kernel with the parameter
vsyscall=emulate
Example with GRUB, modify /etc/default/grub :
GRUB_CMDLINE_LINUX_DEFAULT="vsyscall=emulate"
And then run update-grub
Example with systemd-boot, modify your conf in /boot/loader/entries and add the parameter to the options line :
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options *EXISTINGPARAMS* vsyscall=emulate
answered yesterday
ldclrcq
11
New contributor
ldclrcq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited yesterday
answered yesterday
ldclrcq
11
New contributor
ldclrcq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered yesterday
ldclrcq
11
answered yesterday
ldclrcq
11
11
New contributor
ldclrcq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
ldclrcq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
ldclrcq is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f478387%2frunning-a-centos-docker-image-on-arch-linux-exits-with-code-139%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What does
docker logs <container>show?– slm♦
Oct 29 at 11:55
@slm nothing is returned
– Thomas Crowley
Oct 29 at 12:18
Can you try removing the container and then removing the image and re-downloading it again?
– slm♦
Oct 29 at 12:36
Also make sure SELinux is enabled - bugzilla.redhat.com/show_bug.cgi?id=1488516.
– slm♦
Oct 29 at 12:38
@slm SELinux isn't fully supported with Arch, and the installation process includes about 100 steps, so are you sure this will solve it? wiki.archlinux.org/index.php/…
– Thomas Crowley
Oct 29 at 14:44