Open CpuID opened 8 years ago
Hi,
have the same issue: No errors when running the docker-compose.yml
file with docker-compose
, but errors when using specinfra-backend-docker_compose
which by itself uses docker-compose-api
.
Culprit is this volume definition in the docker-compose.yml
file:
volumes:
- ./service_config:/etc/consul.d
System information:
ruby 2.0.0p384 (2014-01-12) [x86_64-linux-gnu]
docker-compose-api (1.1.2)
Docker version 1.11.1, build 5604cbe
docker-compose version 1.7.1, build 0a9ab35
Ubuntu 14.04.4 LTS
Hello there!
Thanks for submitting the bug!
I'll check it to make sure, but reading the backtrace provided by @CpuID, it seems to be a limitation on Docker client, not compose gem.
Just to clarify: this gem is just a layer running over a Docker client for Ruby. So, all container and image related operations, such as committing an image, starting/stopping containers and managing volumes are performed by this Docker client.
I'll check this issue and, if this is indeed a bug in Docker client, I'll submit a bug to it. In that case, there's nothing I can do to overcome this situation in compose gem.
Thanks in advance!
@mauricioklein thanks - that makes sense actually. Keep us posted :)
Thank you @mauricioklein for your quick response. Looking forward to any updates!
Description
When defining host volumes, an error occurs. Works fine with docker-compose without error.
How to reproduce
Both files can be empty to reproduce the error. Any image can probably be used to simulate the issue also. Using a
.start
call to spin up the "stack".What do you expect
Expected a working set of containers.
What happened instead
Exception fired -
Docker::Error::ServerError
Software:
Full backtrace