Skip to content
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.

Waypoint doesn't find docker-desktop socket #4355

Open
bradydean opened this issue Dec 22, 2022 · 5 comments
Open

Waypoint doesn't find docker-desktop socket #4355

bradydean opened this issue Dec 22, 2022 · 5 comments
Labels
bug Something isn't working plugin/docker upstream

Comments

@bradydean
Copy link

Describe the bug

Waypoint does not use the docket-desktop socket, $HOME/.docker/desktop/docker.sock

waypoint install -platform=docker -accept-tos
❌ Checking for existing installation...
! Error installing server into docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the
  docker daemon running?

Steps to Reproduce

# install docker desktop
sudo dnf install waypoint
waypoint install -platform=docker -accept-tos

Expected behavior

Waypoint server is installed to docker using $HOME/.docker/desktop/docker.sock.

Waypoint Platform Versions

  • Waypoint CLI Version: CLI: v0.10.5 (ece0f75)
  • Waypoint Server Platform and Version: docker
  • Waypoint Plugin: N/A

Additional context

Fedora 37, Docker Desktop 4.15.0 (93002)

@bradydean bradydean added the new label Dec 22, 2022
@evanphx
Copy link
Contributor

evanphx commented Jan 4, 2023

Hi @bradydean,

Are you setting any environment variables (like DOCKER_HOST) to point Waypoint at that path? We're unfamiliar with the path you have there being a standard path for Docker to find that path.

Perhaps this is a new behavior that we haven't picked up support for.

Could you run the following commands and paste the output here?

$ docker context ls
$ docker context inspect
$ docker info
$ docker version

@evanphx evanphx removed the new label Jan 4, 2023
@bradydean
Copy link
Author

No env vars set, just following the docs. The docker socket being in the home directory is pretty common for rootless docker, might even say universal. Idk of an implementation that doesn't put it in the home directory now.

This is from a different machine, but it's still Fedora 37 running Docker Desktop.

[brady@mrc ~]$ docker context ls
NAME                TYPE                DESCRIPTION                               DOCKER ENDPOINT                                  KUBERNETES ENDPOINT   ORCHESTRATOR
default             moby                Current DOCKER_HOST based configuration   unix:///var/run/docker.sock                                            swarm
desktop-linux *     moby                                                          unix:///home/brady/.docker/desktop/docker.sock                         
[brady@mrc ~]$ docker context inspect
[
    {
        "Name": "desktop-linux",
        "Metadata": {},
        "Endpoints": {
            "docker": {
                "Host": "unix:///home/brady/.docker/desktop/docker.sock",
                "SkipTLSVerify": false
            }
        },
        "TLSMaterial": {},
        "Storage": {
            "MetadataPath": "/home/brady/.docker/contexts/meta/fe9c6bd7a66301f49ca9b6a70b217107cd1284598bfc254700c989b916da791e",
            "TLSPath": "/home/brady/.docker/contexts/tls/fe9c6bd7a66301f49ca9b6a70b217107cd1284598bfc254700c989b916da791e"
        }
    }
]
[brady@mrc ~]$ docker info
Client:
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Docker Buildx (Docker Inc., v0.9.1-docker)
  compose: Docker Compose (Docker Inc., v2.13.0)
  dev: Docker Dev Environments (Docker Inc., v0.0.5)
  extension: Manages Docker extensions (Docker Inc., v0.2.16)
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
  scan: Docker Scan (Docker Inc., v0.22.0)

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 20.10.21
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runtime.v1.linux runc io.containerd.runc.v2
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 770bd0108c32f3fb5c73ae1264f7e503fe7b2661
 runc version: v1.1.4-0-g5fd4c4d
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.15.49-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 6
 Total Memory: 3.681GiB
 Name: docker-desktop
 ID: 5AYM:FBQQ:ED6M:WVR3:E2BN:HR6D:J5ZI:RK2A:PDOZ:DE6Q:YOBD:T3KJ
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5000
  127.0.0.0/8
 Live Restore Enabled: false

[brady@mrc ~]$ docker version
Client: Docker Engine - Community
 Cloud integration: v1.0.29
 Version:           20.10.22
 API version:       1.41
 Go version:        go1.18.9
 Git commit:        3a2c30b
 Built:             Thu Dec 15 22:28:45 2022
 OS/Arch:           linux/amd64
 Context:           desktop-linux
 Experimental:      true

Server: Docker Desktop 4.15.0 (93002)
 Engine:
  Version:          20.10.21
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.18.7
  Git commit:       3056208
  Built:            Tue Oct 25 18:00:19 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.10
  GitCommit:        770bd0108c32f3fb5c73ae1264f7e503fe7b2661
 runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

@bradydean
Copy link
Author

I guess it is at an unusual path. Do you know if waypoint is supposed to look at the current docker context or if it just assumes unix:///var/run/docker.sock is correct?

@evanphx
Copy link
Contributor

evanphx commented Jan 4, 2023

We delegate to the official docker golang package to pick up the default, perhaps we need to update that package.

@bradydean
Copy link
Author

Worth a shot

@briancain briancain added bug Something isn't working plugin/docker upstream labels Jan 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working plugin/docker upstream
Projects
None yet
Development

No branches or pull requests

3 participants