Building a container image fails: "container normailzation failed: no manifest.json file found"
Hi all, maybe someone can spot what I am missing.
https://build.opensuse.org/package/show/home:ojkastl_buildservice:distrobox-...
No matter what I do, how often I compare my prjconf with Richard's where he builds some distrobox images, I always end up with the same error: "container normailzation failed: no manifest.json file found" Does anyone have an idea where this comes from? The typo ("normailzation") should make searching easier, but it does not... Kind Regards, Johannes
Johannes Kastl <mail@johannes-kastl.de> writes:
Hi all,
maybe someone can spot what I am missing.
https://build.opensuse.org/package/show/home:ojkastl_buildservice:distrobox-...
No matter what I do, how often I compare my prjconf with Richard's where he builds some distrobox images, I always end up with the same error:
"container normailzation failed: no manifest.json file found"
Does anyone have an idea where this comes from? The typo ("normailzation") should make searching easier, but it does not...
The code is from the OBS backend: https://github.com/openSUSE/open-build-service/blob/457cfd5089e5292f04a9fe36... and it appears like it dies in here: https://github.com/openSUSE/open-build-service/blob/457cfd5089e5292f04a9fe36... So it looks like something is messed up with the container itself. The only thing in the log that I can spot is this line towards the end: [ 252s] skopeo: No such file or directory Could you try to preinstall skopeo? Maybe that'll fix the problem 🤞 Cheers, Dan -- Dan Čermák <dcermak@suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Frankenstr. 146 90461 Nürnberg Germany www.suse.com Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)
Good morning Dan, On 04.07.24 12:24 Dan Čermák wrote:
The code is from the OBS backend: https://github.com/openSUSE/open-build-service/blob/457cfd5089e5292f04a9fe36...
and it appears like it dies in here: https://github.com/openSUSE/open-build-service/blob/457cfd5089e5292f04a9fe36...
So it looks like something is messed up with the container itself.
The only thing in the log that I can spot is this line towards the end: [ 252s] skopeo: No such file or directory
Could you try to preinstall skopeo? Maybe that'll fix the problem 🤞
I already had skopeo in the pre-install but commented it out to follow what Richard currently has in his prjconf.
https://build.opensuse.org/projects/home:RBrownSUSE:containers/prjconf
I just added it back and triggered a rebuild. Failed. I added back umoci, but that build also failed. Kind Regards, Johannes
Hi Johannes, this is the typical sparse file issue. your dockerfile is missing this line at the end: ``` # The go container management tools can't handle sparse files: # https://github.com/golang/go/issues/13548 # If lastlog doesn't exist, useradd doesn't attempt to reserve space, # also in derived containers. RUN rm -f /var/log/lastlog ``` Greetings, Dirk
Hi Dirk, On 05.07.24 13:57 Dirk Mueller wrote:
this is the typical sparse file issue. your dockerfile is missing this line at the end:
``` # The go container management tools can't handle sparse files: # https://github.com/golang/go/issues/13548 # If lastlog doesn't exist, useradd doesn't attempt to reserve space, # also in derived containers.
RUN rm -f /var/log/lastlog ```
Unfortunately it still fails... Kind Regards, Johannes
On 04.07.24 11:15 Johannes Kastl wrote:
https://build.opensuse.org/package/show/home:ojkastl_buildservice:distrobox-...
No matter what I do, how often I compare my prjconf with Richard's where he builds some distrobox images, I always end up with the same error:
"container normailzation failed: no manifest.json file found"
And for whatever reasons, some days after applying Dirk's fix (which did not fix the issue), now the image builds? [ 537s] h02-ch2b finished "build Dockerfile" at Sat Jul 13 10:35:34 UTC 2024. Was there a fix in OBS? Some package update that solved this issue? I really would like to know why this failed, to not have to debug unsuccessfully the next time this issue appears... Kind Regards, Johannes
participants (3)
-
Dan Čermák -
Dirk Mueller -
Johannes Kastl