Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

docker exited with 139 when running cloudera/quickstart:latest

docker exited with 139 when running cloudera/quickstart:latest

New Contributor

I followed the instructions on this link https://www.folio3.ai/blog/up-running-with-cloudera-quickstart-on-docker/ to run cloudera/quickstart from docker image on Windows 10 Version 2004 (Build: 19041.329) and Windows 10 Version: 20H2 (Build 19042.330) and in both platforms the image does not run exiting with 139 error code. I have no idea how to handle that. Please let me know if anyone can help on it.

After pull the image I got this message:

PS C:\Users\xxx> docker pull cloudera/quickstart:latest
latest: Pulling from cloudera/quickstart
Image docker.io/cloudera/quickstart:latest uses outdated schema1 manifest format. Please upgrade to a schema2 image for better future compatibility. More information at https://docs.docker.com/registry/spec/deprecated-schema-v1/
1d00652ce734: Pull complete
Digest: sha256:f91bee4cdfa2c92ea3652929a22f729d4d13fc838b00f120e630f91c941acb63
Status: Downloaded newer image for cloudera/quickstart:latest
docker.io/cloudera/quickstart:latest

11 REPLIES 11
Highlighted

Re: docker exited with 139 when running cloudera/quickstart:latest

Master Collaborator

@EALR Can you share the full error message?


Cheers!
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Highlighted

Re: docker exited with 139 when running cloudera/quickstart:latest

New Contributor

This is the main issue. There is nothing to add. The docker starts the container and ends with 139. No logs, nothing. I tried to put the conditions I am running with the new WSL 2 from Microsoft inside Windows 10 Build greater than 19040. And does not work at all.

Highlighted

Re: docker exited with 139 when running cloudera/quickstart:latest

New Contributor

Same this here. I'm trying to run cloudera in a docker-compose cluster. The yaml looks like this:

 

 

cloudera:
    image: cloudera/quickstart:latest
    hostname: cloudera
    privileged: true
    command: /usr/bin/docker-quickstart
    expose:
      - "8020" # 
      - "8888" # 
      - "9083" # 
      - "10000" # hive jdbc
      - "50070" # nn http
    ports:
      - "8888:8888"
    tty: true
    stdin_open: true
    command: bash -c "/usr/bin/docker-quickstart"

 

 When I run dock-compose up. it silently exits with 139. Using verbose I was able to get the following which is still not very helpful as far as I can see:

 

 docker-compose --verbose start cloudera
compose.config.config.find: Using configuration files: ./docker-compose.yml
docker.utils.config.find_config_file: Trying paths: ['/home/user1/.docker/config.json', '/home/user1/.dockercfg']
docker.utils.config.find_config_file: Found file at path: /home/user1/.docker/config.json
docker.auth.load_config: Found 'credsStore' section
urllib3.connectionpool._make_request: http://localhost:None "GET /v1.22/version HTTP/1.1" 200 875
compose.cli.command.get_client: docker-compose version 1.25.5, build 8a1c60f6
docker-py version: 4.1.0
CPython version: 3.7.5
OpenSSL version: OpenSSL 1.1.0l  10 Sep 2019
compose.cli.command.get_client: Docker base_url: http+docker://localhost
compose.cli.command.get_client: Docker version: Platform={'Name': 'Docker Engine - Community'}, Components=[{'Name': 'Engine', 'Version': '19.03.8', 'Details': {'ApiVersion': '1.40', 'Arch': 'amd64', 'BuildTime': '2020-03-11T01:29:16.000000000+00:00', 'Experimental': 'false', 'GitCommit': 'afacb8b', 'GoVersion': 'go1.12.17', 'KernelVersion': '4.19.104-microsoft-standard', 'MinAPIVersion': '1.12', 'Os': 'linux'}}, {'Name': 'containerd', 'Version': 'v1.2.13', 'Details': {'GitCommit': '7ad184331fa3e55e52b890ea95e65ba581ae3429'}}, {'Name': 'runc', 'Version': '1.0.0-rc10', 'Details': {'GitCommit': 'dc9208a3303feef5b3839f4323d9beb36df0a9dd'}}, {'Name': 'docker-init', 'Version': '0.18.0', 'Details': {'GitCommit': 'fec3683'}}], Version=19.03.8, ApiVersion=1.40, MinAPIVersion=1.12, GitCommit=afacb8b, GoVersion=go1.12.17, Os=linux, Arch=amd64, KernelVersion=4.19.104-microsoft-standard, BuildTime=2020-03-11T01:29:16.000000000+00:00
compose.cli.verbose_proxy.proxy_callable: docker inspect_network <- ('project3_default')
urllib3.connectionpool._make_request: http://localhost:None "GET /v1.22/networks/project3_default HTTP/1.1" 200 1716
compose.cli.verbose_proxy.proxy_callable: docker inspect_network -> {'Attachable': False,
 'ConfigFrom': {'Network': ''},
 'ConfigOnly': False,
 'Containers': {'1d5c500c0e0ad94b0c66a4ff9524bfcfe1323c762a4b63444a66822b12e5c60c': {'EndpointID': 'ba49e9233aa1f4cba2ba6569fa36514b7e0cb412fef92e1c0755e35aac3adfb0',
                                                                                     'IPv4Address': '172.18.0.5/16',
                                                                                     'IPv6Address': '',
                                                                                     'MacAddress': '02:42:ac:12:00:05',
                                                                                     'Name': 'project3_zookeeper_1'},
                '2dc3c508b4c8fb6bb8163c968179185c5e1a3b753f08a6ab3c31b0d802ee9a54': {'EndpointID': '2355f170495a5762deb7445f632b68a1e691992816d3ff92d888332540a9d940',
                                                                                     'IPv4Address': '172.18.0.6/16',
...
Starting cloudera ...
compose.parallel.feed_queue: Pending: {<Service: cloudera>}
compose.parallel.feed_queue: Starting producer thread for <Service: cloudera>
compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=True, filters={'label': ['com.docker.compose.project=project3', 'com.docker.compose.service=cloudera', 'com.docker.compose.oneoff=False']})
urllib3.connectionpool._make_request: http://localhost:None "GET /v1.22/containers/json?limit=-1&all=1&size=0&trunc_cmd=0&filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Dproject3%22%2C+%22com.docker.compose.service%3Dcloudera%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D HTTP/1.1" 200 1269
compose.cli.verbose_proxy.proxy_callable: docker containers -> (list with 1 items)
compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- ('3dd42eaab54bd0612e2ed19bcbda1db8e979edde763136e08869c37da2ef248e')
urllib3.connectionpool._make_request: http://localhost:None "GET /v1.22/containers/3dd42eaab54bd0612e2ed19bcbda1db8e979edde763136e08869c37da2ef248e/json HTTP/1.1" 200 None
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {'AppArmorProfile': '',
 'Args': ['bash', '-c', '/usr/bin/docker-quickstart'],
 'Config': {'AttachStderr': False,
            'AttachStdin': False,
            'AttachStdout': False,
            'Cmd': ['bash', '-c', '/usr/bin/docker-quickstart'],
            'Domainname': '',
            'Entrypoint': ['/usr/bin/docker-entrypoint'],
            'Env': ['PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin'],
            'ExposedPorts': {'10000/tcp': {},
...
compose.cli.verbose_proxy.proxy_callable: docker start <- ('3dd42eaab54bd0612e2ed19bcbda1db8e979edde763136e08869c37da2ef248e')
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
urllib3.connectionpool._make_request: http://localhost:None "POST /v1.22/containers/3dd42eaab54bd0612e2ed19bcbda1db8e979edde763136e08869c37da2ef248e/start HTTP/1.1" 204 0
compose.cli.verbose_proxy.proxy_callable: docker start -> None
compose.parallel.parallel_execute_iter: Finished processing: <Service: cloudera>
compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=False, filters={'label': ['com.docker.compose.project=project3', 'com.docker.compose.service=cloudera', 'com.docker.compose.oneoff=False']})
urllib3.connectionpool._make_request: http://localhost:None "GET /v1.22/containers/json?limit=-1&all=0&size=0&trunc_cmd=0&filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Dproject3%22%2C+%22com.docker.compose.service%3Dcloudera%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D HTTP/1.1" 200 1570
Starting cloudera ... done
compose.parallel.feed_queue: Pending: set()





Any help would be great!

 

 
Highlighted

Re: docker exited with 139 when running cloudera/quickstart:latest

New Contributor

Same thing happen with me

Highlighted

Re: docker exited with 139 when running cloudera/quickstart:latest

Master Collaborator

@neliodv @EALR The exit code 139 indicates the issue with system more than the docker image. 

Are you getting same issue with any other images as well? Try updating docker version this might resolve the issue. 


Cheers!
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Highlighted

Re: docker exited with 139 when running cloudera/quickstart:latest

New Contributor

No. The other containers run smoothly. In fact, they are pretty smaller than Cloudera/quickstart. The whole problem is that this container is big and my machine has just 16GB. It's a memory issue. The container probably is requiring more memory and because it is not possible to allocate more memory the kernel just kill the container. Either we increase the memory from 16GB to 24GB or 32GB and might solve the problem or configure docker app and Windows to manage this memory limitation properly. However I am beginner in all these techies and have no idea from where to start.

Highlighted

Re: docker exited with 139 when running cloudera/quickstart:latest

New Contributor

I also believe that..

Highlighted

Re: docker exited with 139 when running cloudera/quickstart:latest

New Contributor

As the other users have mentioned, all the other containers work fine. Just cloudera. @GangWar, assuming you have contacts in cloudera, do you know if this is supported?

Highlighted

Re: docker exited with 139 when running cloudera/quickstart:latest

New Contributor

This issue is up till June.

Please find a fix.

I am on Win10 20H2 also with Docker v19.03.12and WSL2
I'm getting the code exited 139 everytime trying to launch the docker instance.

Don't have an account?
Coming from Hortonworks? Activate your account here