#Error : exec docker inspect --type=image registry.dagger.io/engine:v0.11.8 / ! failed to run comman

1 messages · Page 1 of 1 (latest)

wicked jackal
#

Hello everyone, I'm encountering an error when launching my Github Actions workflow, it only occurs in the build / deploy stages.

The error in question is: exec docker inspect --type=image registry.dagger.io/engine:v0.11.8 ERROR [0.0s] / ! failed to run command: exit status 1

It doesn't cause the course to fail, but I'd like to know how to resolve it?

jolly ocean
#

what kind of runner are you using for your jobs? is docker installed on those machines?

wicked jackal
#

Runs-on: ubuntu-latest and no

jolly ocean
#

hm, ubuntu-latest runners should have docker installed 🤔 but yes, running dagger requires an installation of docker so it can automatically start the engine

wicked jackal
#

But the rest of the "actions" don't show any error.

#

exec docker pull registry.dagger.io/engine:v0.11.8
exec docker pull registry.dagger.io/engine:v0.11.8 DONE [7.3s]
249
5 : [7.2s] | 5d89a1eace72: Pull complete
250
5 : [7.3s] | b36a3956bdbc: Pull complete
251
5 : [7.3s] | cd8b0f4a18ad: Pull complete
252
5 : [7.3s] | Digest: sha256:340fc178220763769ffc6e182af8cccb0dd35d735e5b90853ce2315f69b4ce1a
253
5 : [7.3s] | Status: Downloaded newer image for registry.dagger.io/engine:v0.11.8
254
5 : [7.3s] | registry.dagger.io/engine:v0.11.8
255
6 : exec docker run --name dagger-engine-340fc17822076376 -d --restart always -v /var/lib/dagger --privileged -e DAGGER_CLOUD_TOKEN registry.dagger.io/engine:v0.11.8 --debug
256
6 : [0.0s] | 53109a2c79d05d35d4aaa6970d40c422af9060c32bca11aebb8caeb11d27d205
257
6 : exec docker run --name dagger-engine-340fc17822076376 -d --restart always -v /var/lib/dagger --privileged -e DAGGER_CLOUD_TOKEN registry.dagger.io/engine:v0.11.8 --debug DONE [0.3s]
258
3 : create DONE [8.1s]
259
2 : starting engine DONE [8.1s]
260
7 : connecting to engine
261
7 : | engine name=53109a2c79d0 version=v0.11.8 client=7qohvlr8dkdqdf1ossthj79e3
262
7 : | cloud url=https://dagger.cloud/SCAFEDAGGER/traces/80249d40cc4dc20e233fd8acd58c83ce
263
7 : connecting to engine DONE [2.1s]
264
8 : starting session
265
1 : connect DONE [10.3s]
266
#0 building with "default" instance using docker driver

jolly ocean
#

oh i see

#

right, the error you're getting here isn't causing the build to fail

#

why does this need resolving in the first place? the failure is legitimate - this step fails, so dagger then proceeds to pull it

#

if you really want to avoid it, you can docker pull registry.dagger.io/engine:v0.11.8 or whatever version before the dagger call command

#

but this error is non critical, it can be ignored

wicked jackal
#

That's exactly what I did, but I'm still making the same mistake.

#

How to correct or hide it?

jolly ocean
#

the cli and engine versions aren't matching

#

v0.11.8 and v0.11.9 are different

#

if you're pinning to a version, you should set the DAGGER_VERSION env variable in front of sh

wicked jackal
#

Yes, I change the version in the meantime

#

But the problem is still here

jolly ocean
#

i'm not sure i understand why this is an issue though - the image is not local, it needs to be pulled 🤔

#

is the issue that the span fails? or that the logs say "ERROR"?

wicked jackal
#

Logs say "ERROR"

jolly ocean
wicked jackal
#

OK, thanks a lot for your action !