I have a problem with clickable to compile for Noble.
-
Hello all.
When i launch clickable build, now, this error is returned.
Someone who know how to fix it?clickable build
Building app
Trying to pull docker.io/clickable/amd64-utnext-amd64:latest...
Getting image source signatures
Copying blob 65d4a342afc6 skipped: already exists
Copying blob 2726e237d1a3 skipped: already exists
Copying blob ef1511aff115 skipped: already exists
Copying blob a97a4c8acde7 skipped: already exists
Copying blob 4ad0091c00a8 skipped: already exists
Copying blob 3f90e7b1c343 done |
Copying blob 5d1434f01f5d skipped: already exists
Copying blob ce6145f1a750 skipped: already exists
Copying blob fdc55cec6c2e done |
Copying blob 7b414aa65691 skipped: already exists
Copying blob 816505108b6f done |
Copying blob 4f4fb700ef54 done |
Copying blob 21c6e27aaaf0 done |
Copying blob d2570c8e4d29 done |
Copying blob f080f8c5d6c5 done |
Copying blob e40658b5df2f done |
Error: writing blob: adding layer with blob "sha256:fdc55cec6c2e2a040e9852da37324fc6b556e9296863ed812c43724073d8e5bc"/""/"sha256:e9c55a7c1ba23a626b05a9d5c619d85fa9072441be6816632284998fd1019ba9": unpacking failed (error: exit status 1; output: container ID 32011 cannot be mapped to a host ID)
Command exited with non-zero exit status 125, see above for details. This is most likely not a problem with Clickable. -
is your clickable and docker images up to date ?
Maybe some old 20.04 builds there ? i had sometimes to clean the build and .clickable directory to ensure we are ok.
-
@lduboeuf
Thanks for the answer Lionel.
Well, i have made some tries but without success.
Finally, i have remove the pip3 install of 8.3.1 and reinstall with snap and now it's working.
There was something wrong with the blob fdc55cec6c2e
