search

GNS3 / gns3-registry

GNS3 devices registry
GNU General Public License v3.0
323 stars 387 forks source link

docker adosztal network automation is recommended not to be used in an exported project - especially on windows #796

Closed josephmhiggins closed 8 months ago

josephmhiggins commented 11 months ago

Community link: https://gns3.com/community/discussions/do-not-try-to-export-docker-adosztal-network-automation-on-windows-for-gns3-version-le-2-2-41

I am deleting that docker from my windows and ubuntu host. This problem has nothing to do with the recent pull request about sudo.py The problem with this docker exists on windows 10 gns3 version 2.2.39 vmware workstation pro 16.2.5 windows 10 gns3 version 2.2.41 vmware workstation pro 16.2.5 ubuntu 23.04 and gns3 version 2.2.40.1

I will have to wait until export project gets rewritten, but I think - though I know nothing about dockers - there is something wrong with that docker. The log files for the exports on windows 10 are 30,000 lines long in debug mode, so they are not included.

edit: the dockers gns3-endhost and ipterm take "5 seconds" to export on windows 10 - should have been gns3 2.2.39 for gns3-endhost and gns3 2.2.41 for ipterm. I am going have to put all the gns3 dockers in one project, start them, stop them, and then export the project for all gns3 versions henceforth.

Here is the high end of the gns3 marketplace labs:

C:\Users\joe_I7\GNS3\projects\_Gns3Marketplace\IP SLA Static Route with VPN Backup | 41.58 MB -- | -- C:\Users\joe_I7\GNS3\projects\_Gns3Marketplace\Building the ISP network w BGP | 37.57 MB C:\Users\joe_I7\GNS3\projects\_Gns3Marketplace\IS-IS Lab 16 Troubleshooting Multi-Area Solution | 35.73 MB

The low end of the gns3 marketplace - where users just upload gnsa files - begins around here:

C:\Users\joe_I7\GNS3\projects\_Gns3Marketplace\Implementing RIP for IPv6 - RIPng | 7.40 KB -- | -- C:\Users\joe_I7\GNS3\projects\_Gns3Marketplace\HP-Router | 6.99 KB C:\Users\joe_I7\GNS3\projects\_Gns3Marketplace\Campus Network IOS and EXOS | 1.19 KB

All of this stems from this marketplace lab: https://gns3.com/marketplace/labs/network-automation-3 The original poster used gns3/network_automation - which no longer apparently exists. I swapped it out for adosztal/network_automation

I suggest: Please do not approve dockers with underscores in their name - it hoses up a gns3 community post title.

b-ehlers commented 11 months ago

The Dockerfile of adosztal/network_automation includes the line VOLUME [ "/root", "/etc", "/usr" ]. This results in the whole /usr directory tree of the docker image being saved in the project, that's about 700 MB (uncompressed).

The advantage is, that additional ubuntu packages installed in this image are available after project closing and re-opening. "Normal" docker images will loose everything outside the /root directory. So this image behaves more like a qemu VM.

The drawback is a much bigger project disk usage. The export normally needs to compress that and then transfer it from the GNS3 server to the client.

On my 10 years old lame linux computer (local GNS3 server) the project export of a project with just one network_automation image takes about one minute with the default zip compression and less than 30 seconds without compression. So in my installation the export is much faster.