-
-
Notifications
You must be signed in to change notification settings - Fork 792
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
docker_container fails to :run #1146
Comments
@urlund is this only happening on Mac Desktops or does this also happen on Linux desktops using the newer version of Docker? |
@ramereth - I just tested Docker version 19.03.14 on Ubuntu 20.04 (in VirtualBox for Mac) - everything seems to work as expected. |
@urlund what version of the docker-api gem do you have installed? I wonder if you're running into a similar issue we're seeing in test-kitchen/kitchen-dokken#208 |
@ramereth you are right, it's related to the docker-api gem. I modified the docker cookbook to:
And deleted the
|
We'll need to look more closely at what needs to be fixed on our end. Feel free to make a PR if you figure out it and we'll get it reviewed/merged. |
π» Brief Description
Cannot
:run
containers.π₯ Cookbook version
Version: 7.2.2
π©βπ³ Version
Chef: 14.15.6
π© Platform details
Fails on a newer docker version (Server Version: 19.03.13 - docker desktop for mac) but it works on an older version (Server Version: 19.03.12 - debian)
I'm running chef in a docker container and mounts the socket as a volume, like this:
docker run --rm -v /var/run/docker.sock:/var/run/docker.sock username/chef-client
Steps To Reproduce
Steps to reproduce the behavior:
π Expected behavior
I get this on an older docker version (running on debian)
On a newer version (docker desktop) I get this:
β Additional context
I've done some digging and it seems to be an issue with the the response format from the docker socket.
I've previously used the docker cookbook on docker desktop for mac, where everything has been working as expected, thats why I suspect the docker version to be the reason for this issue.
The text was updated successfully, but these errors were encountered: