B. Ehlers

Last week I noticed a large drawback of my solution: As I haven't found a software or python module, that returns the docker image information in a way I need,...

Found a python module to access a Docker registry: [python-dxf](https://pypi.org/project/python-dxf/). I have modified my code to use that module and the first tests are promising. That solves my issue to...

So how can I help? I suggest, that I use my old gns3-docker-build code and create a fork of this registry (and optionally a PR). This gives you a build...

> Your old gns3-docker-build code is not accessible anymore. Also, you mentioned [python-dxf](https://pypi.org/project/python-dxf/) and that your first tests were promising. How close the implementation is ready to be used? Correct,...

OK, I will create a fork of gns3-registry including my docker build system in the next days.

Well, I am faster than expected. I created a fork [b-ehlers/gns3-registry-docker](https://github.com/b-ehlers/gns3-registry-docker) with the build system added. First I used it to upload to the GitHub Container Registry [ghcr.io](https://github.com/b-ehlers?tab=packages), then I...

> Just one question, do you rebuild the images on a.schedule too? > > ``` > schedule: > - cron: '37 7 * * 3' > ``` Yes, there are...

I have to agree, that this part of the workflow file is confusing. The Dockerhub statements are included twice, one time uncommented and therefore active and one time commented in...

Much better now, shows even more appliances than here. The following appliances are shown twice: FortiADC KEMP Free VLM OpenBSD OpenWrt Realview WatchGuard Windows The appliances are partly named slightly...

I had a deeper look into the differences between the marketplace and this registry. Here my detailed report: Marketplace Name | Issue --- | --- EXOS | Old marketplace appliance,...