Product : Cumulocity Microservices
Problem : When i am trying to upload microservice zip file in microservice area under admin tab it is giving me the error [ unable to untar the tar file ].
Product : Cumulocity Microservices
Problem : When i am trying to upload microservice zip file in microservice area under admin tab it is giving me the error [ unable to untar the tar file ].
I think you are not uploading a proper microservice archive. Which binary did you upload? And how did you build it (if built by yourself)?
Hi stefan,
The microservice consist of mainly 4 files :
Command used to create a docker file is :
after this i make a zip file of cumulocity manifest file and the tar file with name as : ml-system.
Can you double check that the zip does not contain a nested folder:
For example I just checked the structure of the cloud-http-proxy microservice, and below shows the zip contents:
% unzip -l ~/"Downloads/cloud-http-proxy.zip"
Archive: ~/Downloads/cloud-http-proxy.zip
Length Date Time Name
--------- ---------- ----- ----
677 03-05-2024 12:17 cumulocity.json
153496576 03-05-2024 12:18 image.tar
--------- -------
153497253 2 files
And if that looks ok, I would also double check that the tar file is readable (in case it was corrupted for some reason):
You can check the image.tar
file by using the following command:
tar tvf ./image.tar
Which should give an output similar to this (the contents will differ for your microservice):
drwxr-xr-x 0/0 0 2024-03-05 12:17 280f9a589e1a4035c9b0c18e1698ee25c6d70673000b0324ab1813c60f980038/
-rw-r--r-- 0/0 3 2024-03-05 12:17 280f9a589e1a4035c9b0c18e1698ee25c6d70673000b0324ab1813c60f980038/VERSION
-rw-r--r-- 0/0 477 2024-03-05 12:17 280f9a589e1a4035c9b0c18e1698ee25c6d70673000b0324ab1813c60f980038/json
-rw-r--r-- 0/0 3584 2024-03-05 12:17 280f9a589e1a4035c9b0c18e1698ee25c6d70673000b0324ab1813c60f980038/layer.tar
drwxr-xr-x 0/0 0 2024-03-05 12:17 3f17fff9220b24cca874a3f4e00f5d8945688f9e9b864dbb6696c92765b2dd86/
-rw-r--r-- 0/0 3 2024-03-05 12:17 3f17fff9220b24cca874a3f4e00f5d8945688f9e9b864dbb6696c92765b2dd86/VERSION
-rw-r--r-- 0/0 981 2024-03-05 12:17 3f17fff9220b24cca874a3f4e00f5d8945688f9e9b864dbb6696c92765b2dd86/json
-rw-r--r-- 0/0 71168 2024-03-05 12:17 3f17fff9220b24cca874a3f4e00f5d8945688f9e9b864dbb6696c92765b2dd86/layer.tar
drwxr-xr-x 0/0 0 2024-03-05 12:17 42ed87b0ea80efdee2f95180fb3324c42f95d7bdc7dfc078650c0395b73ad227/
-rw-r--r-- 0/0 3 2024-03-05 12:17 42ed87b0ea80efdee2f95180fb3324c42f95d7bdc7dfc078650c0395b73ad227/VERSION
-rw-r--r-- 0/0 401 2024-03-05 12:17 42ed87b0ea80efdee2f95180fb3324c42f95d7bdc7dfc078650c0395b73ad227/json
-rw-r--r-- 0/0 7667200 2024-03-05 12:17 42ed87b0ea80efdee2f95180fb3324c42f95d7bdc7dfc078650c0395b73ad227/layer.tar
drwxr-xr-x 0/0 0 2024-03-05 12:17 541dc08a2edd6f3b485885645405a2acd8c1117d0bd25b863ad7efdc64abae94/
-rw-r--r-- 0/0 3 2024-03-05 12:17 541dc08a2edd6f3b485885645405a2acd8c1117d0bd25b863ad7efdc64abae94/VERSION
-rw-r--r-- 0/0 477 2024-03-05 12:17 541dc08a2edd6f3b485885645405a2acd8c1117d0bd25b863ad7efdc64abae94/json
-rw-r--r-- 0/0 118817792 2024-03-05 12:17 541dc08a2edd6f3b485885645405a2acd8c1117d0bd25b863ad7efdc64abae94/layer.tar
-rw-r--r-- 0/0 7002 2024-03-05 12:17 67119d34d866ae4eee062baf307245d8fc3ed514fe00869774e3865b60e4c91a.json
drwxr-xr-x 0/0 0 2024-03-05 12:17 80d70a594c960458917b39be588deee8a0a3c55805bab1a66a1e313a36d58e4b/
-rw-r--r-- 0/0 3 2024-03-05 12:17 80d70a594c960458917b39be588deee8a0a3c55805bab1a66a1e313a36d58e4b/VERSION
-rw-r--r-- 0/0 477 2024-03-05 12:17 80d70a594c960458917b39be588deee8a0a3c55805bab1a66a1e313a36d58e4b/json
-rw-r--r-- 0/0 19106304 2024-03-05 12:17 80d70a594c960458917b39be588deee8a0a3c55805bab1a66a1e313a36d58e4b/layer.tar
drwxr-xr-x 0/0 0 2024-03-05 12:17 cad007abb99d0272d367ef2845a7df61a095a7d65d2b22a043ea9f0dd989daff/
-rw-r--r-- 0/0 3 2024-03-05 12:17 cad007abb99d0272d367ef2845a7df61a095a7d65d2b22a043ea9f0dd989daff/VERSION
-rw-r--r-- 0/0 477 2024-03-05 12:17 cad007abb99d0272d367ef2845a7df61a095a7d65d2b22a043ea9f0dd989daff/json
-rw-r--r-- 0/0 7800320 2024-03-05 12:17 cad007abb99d0272d367ef2845a7df61a095a7d65d2b22a043ea9f0dd989daff/layer.tar
-rw-r--r-- 0/0 597 1970-01-01 01:00 manifest.json
-rw-r--r-- 0/0 99 1970-01-01 01:00 repositories
The Push failed on image
is a known issue with docker engine v25.
Consider downgrading to v24 for now.
Echoing Tristan’s info, the fix for the docker 25 problem will be in these versions…
Fix versions
10.17.0.455
10.18.0.349
10.16.0.448
…and the upcoming y2024 version.
Hi i am using docker version v4.28.0 and there is no option to install docker desktop version 4.24 ?
Hi,
the colleagues are referring to v25 of the docker-engine while your version seems to be the version of Docker desktop.
Docker Desktop v4.28 is using v25 engine:
According to Docker Desktop release notes | Docker Docs , Docker Desktop v4.27 started to use v25 engine. So you’d have to downgrade to anything below this version until the Fix mentioned by Robert reached your Cumulocity instance.
I am running 10.18.0.356 and it still doesn’t seem to be fixed, despite 10.18.0.349+ supposedly fixing the issue?
Any insight as to which versions have / will contain the fix?
10.18.0.356 of what? Frontend? Backend? Microservice SDK?
Sorry I was referencing the Backend.
Frontend 1018.0.233
Backend 1018.0.356
Not using the SDK, just a Python based Microservice based on FastAPI.
Experiencing the issue described and required a downgrade to Docker Engine <25 to get it working.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.