Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crate in Docker does not work #7922

Closed
pisaia01 opened this issue Nov 23, 2018 · 2 comments
Closed

Crate in Docker does not work #7922

pisaia01 opened this issue Nov 23, 2018 · 2 comments

Comments

@pisaia01
Copy link

CrateDB version: 3.1.2

Environment description: Ubuntu 18.04.1 using Docker

  • JVM version: 1.8.0_191
  • Kernel: Linux 4.15.0-29-generic
  • Distribution: Ubuntu 18.04.1 LTS
  • Docker: 18.09.0 build 4d60db4

Problem description:

crate does not work when using docker. Cannot access it either using commands or even on the web browser using the localhost:4201

I am using sudo docker network create crate which works because the result of the command sudo docker network ls give

NETWORK ID          NAME                DRIVER              SCOPE
34cbc4b7b1bc        bridge              bridge              local
630b802ef3d1        crate               bridge              local
5bd9f212f4c3        host                host                local
2c63202ab0ea        none                null                local

Then I run the command

sudo docker run -d --name=crate01 \
      --net=crate -p 4201:4200 --env CRATE_HEAP_SIZE=2g \
      crate -Cnetwork.host=_site_

This also works, and the sudo docker ps command gives the following output in the first seconds

CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS                            PORTS                                        NAMES
e89574eeefcf        crate               "/docker-entrypoint.…"   4 seconds ago       Up 2 seconds (health: starting)   4300/tcp, 5432/tcp, 0.0.0.0:4201->4200/tcp   crate01

But I cannot access docker through http://localhost:4201/, it says unable to connect.
Also if I re-run the sudo docker ps command after 20-30 seconds the output becomes

CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
@mfussenegger
Copy link
Member

Do you have some logs? It looks like the process dies for some reason

@no-response
Copy link

no-response bot commented Dec 14, 2018

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@no-response no-response bot closed this as completed Dec 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants