-
Notifications
You must be signed in to change notification settings - Fork 18.9k
testing: update docker-py 6.1.3 #43998
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
Conversation
|
Yup, this won't work; Perhaps it's time to move the docker-py tests outside of docker-in-docker (perhaps even run them on github actions if we already have code there to spin up the docker daemon) |
|
building the docker-py image now happens on GitHub actions, so moving this out of draft 👍 |
Ah, sorry, I was wrong; while it moved to GitHub actions, we're still building the image docker-in-docker, using the classic builder; So still some work needed there |
6b45532 to
803789c
Compare
|
1 Failure (and some XFAIL, but those can probably be ignored) |
|
Remaining skips need a new release of docker-py;
|
|
Right, so that one failure continues: Hm, right, so error is:
|
Our dev-container now has buildx installed, so we're no longer limited to 17.06. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
release notes: https://github.com/docker/docker-py/releases/tag/6.0.1 full diff: docker/docker-py@5.0.3...6.0.1 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
…socket_ws
Tests are failing with this error:
E ValueError: scheme http+docker is invalid
Which is reported in docker-py in docker/docker-py#1478.
Not sure what changed in the tests, but could be due to updated Python
version or dependencies, but let's skip it for now.
Test failure:
___________ AttachContainerTest.test_run_container_reading_socket_ws ___________
tests/integration/api_container_test.py:1245: in test_run_container_reading_socket_ws
pty_stdout = self.client.attach_socket(container, opts, ws=True)
docker/utils/decorators.py:19: in wrapped
return f(self, resource_id, *args, **kwargs)
docker/api/container.py:98: in attach_socket
return self._attach_websocket(container, params)
docker/utils/decorators.py:19: in wrapped
return f(self, resource_id, *args, **kwargs)
docker/api/client.py:312: in _attach_websocket
return self._create_websocket_connection(full_url)
docker/api/client.py:315: in _create_websocket_connection
return websocket.create_connection(url)
/usr/local/lib/python3.7/site-packages/websocket/_core.py:601: in create_connection
websock.connect(url, **options)
/usr/local/lib/python3.7/site-packages/websocket/_core.py:245: in connect
options.pop('socket', None))
/usr/local/lib/python3.7/site-packages/websocket/_http.py:117: in connect
hostname, port, resource, is_secure = parse_url(url)
/usr/local/lib/python3.7/site-packages/websocket/_url.py:62: in parse_url
raise ValueError("scheme %s is invalid" % scheme)
E ValueError: scheme http+docker is invalid
------- generated xml file: /src/bundles/test-docker-py/junit-report.xml -------
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
full diff: docker/docker-py@6.0.1...6.1.3 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
|
Itsa greeeeeen ✅ ✅ ✅ |
🤞 hope this is gonna work, because the CLI inside the container is 17.06, and docker/docker-py@cd2c35a changed the Dockerfile we build to depend on BuildKit features (
--mount)testing: update docker-py 6.0.1
release notes: https://github.com/docker/docker-py/releases/tag/6.0.1
full diff: docker/docker-py@5.0.3...6.0.1
testing: update docker-py 6.1.3
full diff: docker/docker-py@6.0.1...6.1.3
- A picture of a cute animal (not mandatory but encouraged)