Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
new docker install won't run - Exited (139)
#1
Ran the following command per 1.5 Installation under Docker on
https://wiki.pandorafms.com/index.php?ti...Installing

curl -sSL http://pandorafms.org/getpandora  | sh

The container is installed, but every time I start it, it exits with code 139. 

CONTAINER ID        IMAGE                     COMMAND                  CREATED             STATUS                        PORTS               NAMES
72ae3a2851e7        pandorafms/pandorafms:7   "/bin/bash /entrypoi…"   26 minutes ago      Exited (139) 21 minutes ago                       pandorafms


Any thoughts?

Appreciate the help
 Reply
#2
(10-25-2018, 01:38 AM)mankiko7 Wrote: Ran the following command per 1.5 Installation under Docker on
https://wiki.pandorafms.com/index.php?ti...Installing

curl -sSL http://pandorafms.org/getpandora  | sh

The container is installed, but every time I start it, it exits with code 139. 

CONTAINER ID        IMAGE                     COMMAND                  CREATED             STATUS                        PORTS               NAMES
72ae3a2851e7        pandorafms/pandorafms:7   "/bin/bash /entrypoi…"   26 minutes ago      Exited (139) 21 minutes ago                       pandorafms


Any thoughts?

Appreciate the help
Good morning mankiko7,

Try to do the steps describe in the link below and then tell us the result of them.

https://stackoverflow.com/questions/4672...s-code-139

If it still persist, do you have any problems when unistalling and installing the docker? problem maybe with the install.php.

Alberto
 Reply
#3
(10-25-2018, 08:00 AM)alberto.sanchez Wrote: Good morning mankiko7,

Try to do the steps describe in the link below and then tell us the result of them.

https://stackoverflow.com/questions/4672...s-code-139

If it still persist, do you have any problems when unistalling and installing the docker? problem maybe with the install.php.

Alberto

Thanks for the suggestion Alberto

Even when I override the entrypoint to /bin/bash, it still exits immediately:
docker run -it --entrypoint=/bin/bash pandorafms/pandorafms:7

CONTAINER ID                                                       IMAGE                     COMMAND             CREATED             STATUS                       PORTS               NAMES

c798b9729d5eb2263139dc37c5aa7c0f4c2e410f37e06b8ec10ddbfa62f21305   pandorafms/pandorafms:7   "/bin/bash"         3 seconds ago       Exited (139) 2 seconds ago                       serene_

Is there some other entrypoint I should try?

From what I can tell my docker installation is OK.  I can run the hello-world and centos containers without issue.  Are there any other containers I should try to test out PHP?

Dave
 Reply
#4
(10-26-2018, 01:18 AM)mankiko7 Wrote:
(10-25-2018, 08:00 AM)alberto.sanchez Wrote: Good morning mankiko7,

Try to do the steps describe in the link below and then tell us the result of them.

https://stackoverflow.com/questions/4672...s-code-139

If it still persist, do you have any problems when unistalling and installing the docker? problem maybe with the install.php.

Alberto

Thanks for the suggestion Alberto

Even when I override the entrypoint to /bin/bash, it still exits immediately:
docker run -it --entrypoint=/bin/bash pandorafms/pandorafms:7

CONTAINER ID                                                       IMAGE                     COMMAND             CREATED             STATUS                       PORTS               NAMES

c798b9729d5eb2263139dc37c5aa7c0f4c2e410f37e06b8ec10ddbfa62f21305   pandorafms/pandorafms:7   "/bin/bash"         3 seconds ago       Exited (139) 2 seconds ago                       serene_

Is there some other entrypoint I should try?

From what I can tell my docker installation is OK.  I can run the hello-world and centos containers without issue.  Are there any other containers I should try to test out PHP?

Dave

Good morning mankiko7,

What version of docker do you have?¿ have to tried to upgrade to latest docker version and try it?
Ill just downloaded docker and used the wiki an everything went correct.

Have you tried also to disable the firewall and selinux?

Alberto
 Reply
#5
Morning Alberto -
Docker version is 18.06.1-ce, build e68fc7a
This is running on debian stretch (9.1). No selinux

Installed docker-ce last week per the instructions here:
https://docs.docker.com/install/linux/do...ocker-ce-1

Looks like I have the latest docker version from the repo:
[email protected] ➜ ~ apt-cache madison docker-ce
docker-ce | 18.06.1~ce~3-0~debian | https://download.docker.com/linux/debian stretch/stable amd64

Maybe I will try running some other containers to see if those work

Appreciate your help so far and prompt responses
Dave
 Reply
#6
(10-26-2018, 11:17 AM)mankiko7 Wrote: Morning Alberto -
Docker version is 18.06.1-ce, build e68fc7a
This is running on debian stretch (9.1).  No selinux

Installed docker-ce last week per the instructions here:
https://docs.docker.com/install/linux/do...ocker-ce-1

Looks like I have the latest docker version from the repo:
[email protected] ➜  ~ apt-cache madison docker-ce
docker-ce | 18.06.1~ce~3-0~debian | https://download.docker.com/linux/debian stretch/stable amd64

Maybe I will try running some other containers to see if those work

Appreciate your help so far and prompt responses
Dave

Good morning mankiko7,

I tried with the installation of only docker, not the docker-ce and it worked perfectly.

Please try to run other containers and tell us the results, its possible that the docker runs badly.

Alberto
 Reply
#7
Good makinko7,

Maybe it's a little late but a colleague of ours has found a solution to this problem. The failure is due to a difference between the containers used by Pandora (from CentOS 6) and it seems that in the new distributions these containers don't work properly.

The solution lies in executing this command:

cat /usr/src/linux-headers-$(uname -r)/.config | grep VSYSCALL

In case you get something out of this:

# CONFIG_LEGACY_VSYSCALL_EMULATE is not set

So we don't have it configured, we can fix it by putting the following line in /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="vsyscall=emulate"

Or we can edit the existing one:

GRUB_CMDLINE_LINUX_DEFAULT= quit splash vsyscall=emulate

After reboot should work everything to perfection!

Greetings
Diego
 Reply


Users browsing this thread: 1 Guest(s)


(c) 2006-2018 Artica Soluciones Tecnológicas. Contents of this wiki are under Create Common Attribution v3 licence. | pandorafms.com | pandorafms.org

Theme © MyBB Themes