mix loopyard.setup tries to install Docker Desktop when OrbStack is already running

Aberta
#86 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
62/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Pouca atividade
Stack de tecnologia
docker, elixir
Domínio
cli, devops

Direção de pesquisa

Comece pelo ponto de entrada mix loopyard.setup e inspecione o Brewfile incluído no repositório e a etapa "Brewfile dependencies". Reproduza com um contexto Docker do OrbStack e verifique se setup ignora o cask do Docker Desktop quando as sondas do Docker e do Compose são bem-sucedidas; confirme que o setup completo e a resposta de /system/docker continuam funcionando.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

What happened?
On a working OrbStack installation, mix loopyard.setup aborts during "Brewfile dependencies." The checked-in Brewfile unconditionally includes cask "docker" (now renamed to docker-desktop), so Homebrew tries to install Docker Desktop even though docker version, the orbstack context, and docker compose version already work.

The Docker Desktop cask then collides with OrbStack's existing credential helper:

Installing docker has failed!
Error: docker-desktop: It seems there is already a Binary at '/usr/local/bin/docker-credential-osxkeychain'.
** (Mix) Brewfile dependencies failed

This reproduced identically on two consecutive setup runs. It is adjacent to, but distinct from, the DOCKER_HOST documentation/runtime-detection work tracked in #72: setup fails before daemon connectivity becomes relevant.

Steps to reproduce

  1. Install and start OrbStack on macOS.
  2. Confirm docker version, docker context show (returns orbstack), and docker compose version succeed.
  3. Clone Loopyard.
  4. Run mix loopyard.setup.
  5. Observe Homebrew attempt to install Docker Desktop and setup abort.

Expected behavior
When a usable Docker daemon and Compose implementation are already available, setup should preserve the user's selected runtime and skip the Docker Desktop cask. One possible implementation is to pass HOMEBREW_BUNDLE_CASK_SKIP=docker when a Docker probe succeeds.

The complete setup succeeds today with this workaround:

HOMEBREW_BUNDLE_CASK_SKIP=docker mix loopyard.setup

Afterward, PORT=4001 mix loopyard.server started successfully and /system/docker returned HTTP 200 with Docker.Observer connected to OrbStack.

Environment

  • OS: macOS 26.7 (25G220), Apple Silicon
  • Docker: OrbStack 2.2.3; Docker Engine 29.4.0; Compose v5.1.2
  • Homebrew: 6.0.18-90-g44d5dd8
  • Elixir: 1.20.3 / OTP 29
  • Loopyard: 8bc934a5c041f4ae53706a7524672936cebaa591

Screenshots
Not applicable; terminal output above.

Linguagem predominante
Elixir
Estrelas
85
Forks
11
Métricas de merge de PRs
Nenhum PR com merge em 30d

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de loopyard/loopyard

Todas as issues de loopyard/loopyard

Issues semelhantes

Mais issues de Elixir

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.