#Force re-installing dagger-engine locally

1 messages · Page 1 of 1 (latest)

old halo
#

Hey, so I am running Dagger (v.0.11.0) on Docker Desktop on macOS and I had to clear out all settings and data. Effectively, the dagger-engine is gone.

Now when running any dagger commands, the process hangs waiting for the because it can't find the dagger-engine, but it won't reinstall it.

What is the correct way there any way to force re-installing it? I haven't dug in the dagger-cli code, yet, but where does it store its config so I can clear that out and hopefully force a reinstall?

rough gyro
old halo
#

Nothing

docker ps -a
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
#

So I am now building from source (v0.11.0). I am getting a different error, where the compile distribution binary just hangs.

# 
➜  dagger git:((v0.11.0)) go run ./cmd/dagger run date
● connect 0.5s

11:28:36 WRN failed to resolve image; falling back to leftover engine error="GET https://registry.dagger.io/v2/engine/manifests/latest: MANIFEST_UNKNOWN: manifest unknown"
start engine: no fallback container found
exit status 1
# 
➜  ci git:(feat/PL-2527/evaluate-dagger) dagger version
dagger v0.11.0 (registry.dagger.io/engine) darwin/arm64
➜  ci git:(feat/PL-2527/evaluate-dagger) dagger run date
● connect 8.5s

11:30:37 WRN canceling... (press again to exit immediately)
11:30:37 WRN canceling... (press again to exit immediately)
11:30:37 WRN exiting immediately
#

So I think the issue is that dagger-cli is trying to install the latest version, but it doesn't exists:

➜  ci git:(feat/PL-2527/evaluate-dagger) docker pull registry.dagger.io/engine:latest
Error response from daemon: manifest unknown

vs

➜  ci git:(feat/PL-2527/evaluate-dagger) docker pull registry.dagger.io/engine:v0.11.0
v0.11.0: Pulling from engine
c6b39de5b339: Pull complete
c930ba0a7603: Pull complete
f6c592ed8817: Pull complete
1edc04e5574d: Pull complete
940e9b4e26b0: Pull complete
5866c02bd770: Pull complete
17e51a86d234: Pull complete
1e504367f385: Pull complete
902f3fb3e13b: Pull complete
88d58a103723: Pull complete
1d29c3c345fe: Pull complete
352295ca7461: Pull complete
f571f31723e0: Pull complete
0e3a078e1e5f: Pull complete
d24714424c62: Pull complete
507ebea82b18: Pull complete
a7078b3d16a4: Pull complete
613c7e3b88b8: Pull complete
475944fdfb82: Pull complete
8cc5593c1058: Pull complete
4f4fb700ef54: Pull complete
4c5bb04b3a62: Pull complete
Digest: sha256:9cf4d4ecdf5b646b310bdbc6d4249f7dc0faa31a0039a779df7868f624174898
Status: Downloaded newer image for registry.dagger.io/engine:v0.11.0
registry.dagger.io/engine:v0.11.0
#

So the latest tag got messed up on your registry?

#

Nevermind, the tag version is probably because I am building from source

rough gyro
old halo
#

Nope, that being said looks like running docker pull registry.dagger.io/engine:v0.11.0 manually did fix the issue. 🤷‍♂️

rough gyro
#

the dagger call should have pulled and started the engine automatically

old halo