Jim Cottrell

You might consider checking out [Visual Studio Code remote development](https://code.visualstudio.com/docs/remote/containers) if you like Visual Studio Code, which I do. I had to do a little tweaking to get it how...

As a note, I was getting this same error, but it started working after I removed the existing sensor volume. I'm not sure why that made a difference, because there...

Sounds good, thanks. I'll see how the next version works out. We're still having some build issues, but it looks like if we set a `DOCKER_API_VERSION` environment variable, we can...

For reference, other versions may work (`1.44` did not), but we seem to be back in business with ``` export DOCKER_API_VERSION='1.25' ``` in our pipeline

I've tried with v1.41.1 and no explicit `DOCKER_API_VERSION` and I get that same error: `client version 1.12 is too old`

@kcq Sorry for the delay in responding. As noted before, this is happening only on a self-hosted Bitbucket pipeline runner (linux/amd64). When I run locally, I have no issue. To...

Here's a simplified version of our `bitbucket-pipelines.yml` that fails with `client version 1.12 is too old`: ```yaml image: name: atlassian/default-image:4 definitions: services: privileged-docker: type: docker image: name: docker:dind pipelines: custom:...