Image trouble ? error pulling image configuration: unknown blob

[Fanch-]

First thank you for the effort put into this ! I can't wait to get it to work, especially in this 'period'.

Following the server instructions and running docker-compose up I get :

Pulling migrate (livxtrm/devicefarmer:latest)...
latest: Pulling from livxtrm/devicefarmer
171857c49d0f: Pulling fs layer
419640447d26: Pulling fs layer
61e52f862619: Pulling fs layer
e026d48ac6f8: Waiting
9e051ac05285: Waiting
8b25c2d66269: Waiting
949c72d47c80: Waiting
d139283fb81d: Waiting
2f4fb7ee4390: Waiting
19d98ecf5fc8: Waiting
906be0dc70f1: Waiting
2becb24428a2: Waiting
1d2e3217ed13: Waiting
78c03e033126: Waiting
99539f2a64b1: Waiting
4ef6ab0126e4: Waiting
ERROR: error pulling image configuration: unknown blob

It seems to be Service 'storage-temp' failed to build: error pulling image configuration: unknown blob

Ubuntu 18.04
Docker version 19.03.11

[issue-label-bot]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.65. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[romainlouvet]

Hi @Fanch-
Same problem with
Docker 19.03.13
MacOS 10.15.7

[udaykittu]

Hi @nanoscopic

Facing the same error while performing docker-compose up.

ERROR: error pulling image configuration: unknown blob

Kindly support.

[nanoscopic]

This is an upstream OpenSTF / DeviceFarmer STF issue. Please submit a ticket to https://github.com/devicefarmer/stf for support on this issue. This is the wrong repo to ask for support on this particular issue.

This issue has been brought up by a number of people over time. It has something to do with docker of specific versions ignoring the autobuild of the container. It is supposed to build the "storage-temp" container automatically but for some users it does not.

I see nothing wrong with the way it is configured, so I'm not even sure this is an issue with the config. It may be an issue with how docker-compose itself works on specific versions. I've never encountered the issue myself either on the multiple Linux distributions I've tested this one.

I also don't think the way upstream STF ever set this up is correct. The base image for storage-temp to me seems entirely wrong.

Due to #82 I won't be attempting to correct whatever is wrong here. Anyone who learns anything about this please contribute a fix for it as I won't be doing it.

[nanoscopic]

I figured out what the issue here is. One of the upstream images that the docker hub image was built on was deleted. I rebuilt the docker image from the repo and pushed it live again and it works now again.

I did not realize this was an issue as the machines I was testing it on already had the dependent deleted image cached.