Closed smolinari closed 8 years ago
This error seems more related to compose and docker than to OrientDB. I don't think that compose interact directly with ODB, at least it talks with docker (daemon).
Can you attach your compose to the issue?
Do you mean the docker-compose.yml file
?
This is it.
version: '2'
services:
spider:
build: .
container_name: spider
ports:
- "9000:9000"
links:
- orientdb
volumes:
- /src:/spider/src
- /tests:/spider/test
orientdb:
image: orientdb:latest
container_name: orientdb
environment:
ORIENTDB_ROOT_PASSWORD: rootpwd
ports:
- "2424:2424"
- "2480:2480"
Scott
I guess that the first container starts and then try to access to orient, that is still starting up. There's a proposal : https://github.com/docker/docker/issues/21142
Docker currently doesn't provide any built-in way to determine if a container is "alive" in the sense that the service it provides is up and running.
If this is your case, and I think it is, my suggestion is to add a cycle on startup that check orient availability
Ok. I'll look into doing something about the timing.
Scott
Hi,
When I run the ODB docker container (latest) in a docker-compose.yml file with
docker-compose up
, I get these messages returned.And then docker-composer times out with:
If I set `COMPOSE_HTTP_TIMEOUT to a higher value it just sits with the messages given above, then times out later.
Is this normal procedure?
Scott