-
When docker-outside-of-docker feature ends up using `socat` to create a Unix socket ready to use by user in container, you will experience the following inside your terminal:
1. `echo "uname; exit …
-
Hi,
The latest version, version 1.4.2 gives me "nc: bad address '/var/run/postgresql'" on container start, only this version has this error on the stable branch.
I connect to postgres through soc…
-
### Description
Hi, after update to 4.35.1 we discover new issue on Docker Desktop. It starts checking ports that are not blocked but are used to logging communication (listen on 4505). On 4.35.1, wh…
-
- VSCode Version: 1.94.2
- Local OS Version: macOS 14.3.1 (23D60)
- Remote OS Version: ?
- Remote Extension/Connection Type: Containers
Logs
```
[18 ms] Dev Containers 0.388.0 in VS Code 1.94…
-
Hi there,
For the sake of consistency, I'd like to have my local docker be managed via docker-machine. When I try to create and use my local docker-machine using the 'none' driver:
```
docker-machin…
-
I am running both `docker` and `podman` in parallel. When I try to make `testcontainers` to use `podman` by setting the `DOCKER_HOST` environment variable the test still connected to the default `/var…
-
The dockerlaunch socket is recreated as a root-owned volume on docker restart if the docker daemon is unexpectedly killed
-
## Current situation
As commented [here](https://github.com/inspektor-gadget/inspektor-gadget/pull/2398#discussion_r1464318815), the socket path for docker when using the CRI protocol is not config…
-
Check if `/var/run/docker.sock` is a symlink. If it is, the user is probably using Podman and we should `WARN` on that. I want to properly support Podman but we don't yet.
-
I'm currently using a locally-built Consul image, that runs as root, and that includes a couple of Docker health checks. I'm trying to migrate to using the official image, and running into permission…
dmaze updated
3 years ago