cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1670
Views
7
Helpful
10
Replies

IOx Docker Application Issue

Dennis Xitlaly
Level 1
Level 1

Hello, experts!
I'd like to test IOx application on Cisco ISR 4k, but faced a problem while generating IOx app with ioxclient from Cisco.
The test stand is like this: VM with installed docker and ioxclient. Docker successfully downloads the images from hub.docker.com, they start and run locally without problems.
According to the official documentation for converting docker images to IOx application I should use ioxclient. The command like this:

ioxclient docker package mlabbe/iperf:latest .

But in the end it ends with error, loot at the last 4 lines:

ioxclient docker package --layers mlabbe/iperf:latest .
Currently active profile : default
Secure client authentication: no
Command Name: docker-package
Timestamp at DockerPackage start: 1729148627520
No rsa key and/or certificate files provided to sign the package
Input docker image is not signed
Warning: package.yaml not present in project folder. Will attempt to generate one.
Retrieving docker image
Replacing symbolically linked layers in docker rootfs, if any
No symbolically linked layers found in rootfs. No changes made in rootfs
Removing emulation layers in docker rootfs, if any
The docker image is better left in it's pristine state
Generating IOx Layers
Unresolved layer list: []
Layer directory list: [blobs blobs]
Failed to open docker layer archive
Unable to generate IOx layers from docker image
Error while packaging docker layers
Error occurred : open : no such file or directory

Stand specifications:
Linux Version: Ubuntu 20.04.6 LTS
ioxclient version: 1.17.0.0
I would kindly appreciated it if you shared any ideas about the reasons for the issue.
By the way, I tried to use a different OS version, as well as ioxclient version (1.10.1.0) to no awail.

10 Replies 10

gtont
Level 1
Level 1

Did you find a solution? I'm facing the same error.
Tried on Ubuntu 23.10 (within WSL2 on Windows 11) 


Which image are you using? 

This seems to work fine on my machine. Can you try removing the image first and pull it again?
docker image rm {your image} && docker image pull {your image}

Happy to help! Please mark as helpful/solution if applicable.
Get in touch: https://torbjorn.dev

I use networkstatic/iperf3

docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
networkstatic/iperf3 latest 377c80503c6d 6 months ago 82MB

@Torbjørn wrote:

Which image are you using? 

This seems to work fine on my machine. Can you try removing the image first and pull it again?
docker image rm {your image} && docker image pull {your image}


I tried, but with the same error:

Failed to open docker layer archive
Unable to generate IOx layers from docker image
Error while retrieving layers from docker image
Unable to generate envelope package
Error occurred : open : no such file or directory

gtont
Level 1
Level 1

ntop/nprobe:stable (from https://hub.docker.com/r/ntop/nprobe)

I'm also getting same error. I've removed and repulled image.

 

PS C:\Users\xxx\Documents\ftp_root\DNS_PROJECT> docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
technitium/dns-server latest 423f03aa7c79 12 days ago 361MB
internetsystemsconsortium/bind9 9.20 caae52f6529b 2 weeks ago 562MB

PS C:\Users\xxx\Documents\ftp_root\DNS_PROJECT> C:\Users\xxx\Documents\ftp_root\ioxclient.exe docker package technitium/dns-server .
Currently active profile : default
Secure client authentication: no
Command Name: docker-package
Timestamp at DockerPackage start: 1735857898208
Using the package descriptor file in the project dir
Validating descriptor file package.yaml with package schema definitions
Parsing descriptor file..
Found schema version 2.2
Loading schema file for version 2.2
Validating package descriptor file..
File package.yaml is valid under schema version 2.2
Generating IOx package of type docker with layers as rootfs
Replacing symbolically linked layers in docker rootfs, if any
No symbolically linked layers found in rootfs. No changes made in rootfs
Removing emulation layers in docker rootfs, if any
The docker image is better left in it's pristine state
Parsing Package Metadata file : C:\Users\xxx\Documents\ftp_root\DNS_PROJECT\.package.metadata
Updated package metadata file : C:\Users\xxx\Documents\ftp_root\DNS_PROJECT\.package.metadata
No rsa key and/or certificate files provided to sign the package
-------------------------------------------------------------------------
Generating the envelope package
Failed to open docker layer archive
Unable to generate IOx layers from docker image
Error while retrieving layers from docker image
Unable to generate envelope package
Error occurred : open : The system cannot find the file specified.

 

Emmanuel Tychon
Cisco Employee
Cisco Employee

Hello everyone - 

This issue is caused by the directory structure in Docker engine 25.0.0 that has changed. The problem is resolved when the Docker Engine version is downgraded to 24.0.9 or older but this not something we can recommend. 

This issue is not resolved yet but tracked with bug ID https://bst.cisco.com/bugsearch/bug/CSCwj98505 

Thanks,

Emmanuel

Hi, Emmanuel! Thanks very much for this input. I'm not entitled to see CSCwj98505. Can this bug be made public? Is there a estimated time for fix? Thanks again, and happy 2025!

Hello Marcos -- 

Unfortunately I don't have good news at this point. While this bug has been opened back in May 2024, it has not been fixed by engineering because the changes are "substantial" and it may have side effects in multiple places - not just ioxclient.

Engineering is treating this as a "new feature" rather than a "bug fix" and I'm sorry to say that I don't have a clear view of where we are at. I have inquired the engineering team and product management teams, and hope to be able to come back with a more accurate information shortly.

Thank you for your patience and sorry for the inconvenience. 

Emmanuel

 

I confirm issue clears when downgrading to Docker Desktop v4.24.1, which seems to run on Docker Engine v24.0.6.

Emmanuel Tychon
Cisco Employee
Cisco Employee

Hello jawadnur - this answer is not helpful and not welcome, considering that the issue has been already identfied, confirmed, and engineering is aware of the problem.

Your autogenerated answer can be run any anyone, and does not even provide any useful bit of information. 

Please exert caution in your use of AI, and do it only when and where it is relevant or you'll just discredit yourself.

Thanks,
Emmanuel