Cant use Gordon... login problem

Hi

I am trying Docker desktop on a linux mint desktop. I am trying to resolve an nvidia error (Error response from daemon: unknown or invalid runtime name: nvidia) and am told to “Debug this container error with Gordon…”.

My issue is that although I have logged in to docker desktop when I try to use Gordon I get a blue button labeled “Sign in to use Gordon”, clicking it takes me to a web page with the text “You’re almost done! We’re redirecting you to the desktop app. If you don’t see a dialog, click the button below.” and the button below labeled “Proceed to docker Desktop” doesn’t do anything.

Any Ideas what I am doing wrong,

p.s. I have worked through “Sign in to Docker Desktop” page ( Sign in to Docker Desktop | Docker Docs ) and I have tried rebooting and restarting Docker with (sudo systemctl restart docker).

After the login in your browser, you shoul dbe redirected to a callback url that points to Docker Desktop.

Please share the output of docker info. Also I am not sure if gpu support exists for Docker Deskto on Linux.

Wait, that doesn’t start Docker Desktop but the daemon of Docker CE. Are you sure you logged in to Docker Desktop and not to Docker CE maybe even witha different user? Docker Desktop is not a GUI on top of Docker CE, so you don’t even need to install the docker-ce package, not to meniton other packages not maintained and supported by Docker Inc.

Also if you want to use Nvidia GPU, as @meyay, I am also not aware of Nvidia support in Docker Desktop on Linux. It was supported on Windows because WSL2 started to support it.

So if you tried to configure the nvidia runtime for Docker DEsktop, that will not work and you indeed need Docker CE which can indeed be restarted with the command you shared.

If you already had Docker CE installed where you wanted to debug a gpu runtime issue, then you can install Docker Desktop, but it can complicate thing so I usually don’t recommend it. I did it, but it also confused me sometimes. Depending on how you installed Docker CE or other docker variants, you could have a completely different (older) client compared to your Docker Desktop.

here is the output from docker info

Client: Docker Engine - Community
 Version:    29.4.3
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  agent: Docker AI Agent Runner (Docker Inc.)
    Version:  v1.50.0
    Path:     /home/rosie/.docker/cli-plugins/docker-agent
  ai: Docker AI Agent - Ask Gordon (Docker Inc.)
    Version:  v1.20.2
    Path:     /home/rosie/.docker/cli-plugins/docker-ai
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.33.0-desktop.1
    Path:     /home/rosie/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v5.1.3
    Path:     /home/rosie/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.47
    Path:     /home/rosie/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Docker Inc.)
    Version:  v0.3.0
    Path:     /home/rosie/.docker/cli-plugins/docker-desktop
  dhi: CLI for managing Docker Hardened Images (Docker Inc.)
    Version:  v0.0.3
    Path:     /home/rosie/.docker/cli-plugins/docker-dhi
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.31
    Path:     /home/rosie/.docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.0
    Path:     /home/rosie/.docker/cli-plugins/docker-init
  mcp: Docker MCP Plugin (Docker Inc.)
    Version:  v0.40.4
    Path:     /home/rosie/.docker/cli-plugins/docker-mcp
  offload: Docker Offload (Docker Inc.)
    Version:  v0.5.85
    Path:     /home/rosie/.docker/cli-plugins/docker-offload
  pass: Docker Pass Secrets Manager Plugin (beta) (Docker Inc.)
    Version:  v0.0.25
    Path:     /home/rosie/.docker/cli-plugins/docker-pass
  sandbox:  (Docker Inc.)
    Version:  v0.12.0
    Path:     /home/rosie/.docker/cli-plugins/docker-sandbox
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /home/rosie/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.20.4
    Path:     /home/rosie/.docker/cli-plugins/docker-scout

Server:
 Containers: 7
  Running: 0
  Paused: 0
  Stopped: 7
 Images: 7
 Server Version: 29.4.2
 Storage Driver: overlayfs
  driver-type: io.containerd.snapshotter.v1
 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 splunk syslog
 CDI spec directories:
  /etc/cdi
  /var/run/cdi
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 77c84241c7cbdd9b4eca2591793e3d4f4317c590
 runc version: v1.3.5-0-g488fc13e
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.12.76-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 16
 Total Memory: 15.37GiB
 Name: docker-desktop
 ID: f9b40ba9-47c6-4b72-83d0-c0efffbe9164
 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
 Labels:
  com.docker.desktop.address=unix:///home/rosie/.docker/desktop/docker-cli.sock
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  ::1/128
  127.0.0.0/8
 Live Restore Enabled: false

When I start docker desktop I have to login, it uses a page that looks like a google login window, it is the same as the one used to login to this forum. I have noticed the desktop window that opens still has a login button. I am starting to wonder what I am logging into, this is the Docker desktop I am looking at.

Clicking login in the Docker desktop takes me to a browser page https://auth.docker.com/desktop/redirect?code=X5kkXTEWvINQHX4A5qdkZUF-7IIAjhyvMZkSLqhiEYxip&state=M_hXs6HpIy7IN8sP6LSZfufLoAAEKbFSWkAmq-nVSDM

It has an accompanying popup asking to “Allow this site to open the Docker-desktop link with Docker URL Handler?” This box has to be be allowed to get to the “Proceed to Docker Desktop” button, which doesn’t do anything.

When I installed docker I couldn’t get the desktop to install without first stepping through the non-desktop instructions for Install Docker Engine on Ubuntu Install Docker Engine on Ubuntu | Docker Docs .

Interessting that it doesn’t do the last bit that actually is reponsible to send the login information to Docker Desktop.

Does it mean you executed the commands to potentially cleanup ab old existing docker installation and then continued the docs in Install Docker Desktop on Linux | Docker Docs? Technically, the standalone Docker Engine can be installed on the same time as Docker Desktop, though we don’t recommend installing both on the same system, because it often ends up confusing users that migh use different `docker context’ configurations for their unprivliged and privleged users.

It is kind of odd that your client and server version are not identical, which indicates that you propably indeed had a standalone Docker Engine installation on the host as well. Though, I don’ see how this would interfere with the Docker Desktop Sign-in.

If it’s okay to loose the 7 containers you have created in Docker Desktop, I would try if deleting the standalone Docker Engine, and performaing a Docker Desktop Factory Reset might sort it out.

Yes that was true for my first attempt, I have since set up a linux mint install which I use to try and figure this out.. i.e. I can easily reinstall mint and start again.

It isnt a problem, this install is purely for testing (attempting) to install a self-hosted-ai-starter-kit (from GitHub - theaiautomators/self-hosted-ai-starter-kit: The Self-hosted AI Starter Kit is an open-source template that quickly sets up a local AI environment. Curated by n8n, it provides essential tools for creating secure, self-hosted AI workflows. · GitHub ) so I can start from a fresh install, roll back the os to the point of install if needed.

My method of installing the Docker desktop is to download the docker-desktop-amd64.deb package and let the “package installer” do the work. If there is another - better way I an happy to give it a go as well.

Docker DEsktop only needs you to add the apt repsository, but users often misunderstand that and continue with the installation of the whole engine as the link points to the Docker Engine installation guide where the repository installation is described. Installing the whole engine is not required. As far as I remember, the client doesn’t have to be installed either, only the repository has to be added to apt so the Docker Deskop installer can install the right client that matches the daemon version in Docker Desktop.

I don’t know why it can happen sometimes, but it just happened to me yesterday. I should have checked the logs as I always recommend others, but I was lazy enough to just stop Docker Desktop and see what happens when I start it again. Then I think I just clicked on the login button and suddenly I was logged in.

It looks like I had installed Docker desktop on top of the non-desktop version, once the system was reinstalled with a new Docker the problem was resolved.

Thanks for the replies.