Make it available as an OCI artifact?

[thomaseizinger]

I've been using edgeshark extensively for debugging my application in docker compose and it is great! Over time, my compose file has grown however and I am looking for ways to tidy things up, including the added containers from edgeshark.

I came across the following in the docker compose docs: https://docs.docker.com/compose/how-tos/oci-artifact/#start-an-oci-artifact-application

It sounds like a great fit for edgeshark as it would allow people to include it in their compose file without having to copy in the container definitions.

[thediveo]

Thank you very much for making me aware of this mechanism, I'll look into it!

[thediveo]

@thomaseizinger you've not been forgotten. I've had some success in bringing it to my personal project thediveo/lxkns first, so in case things break I don't get burned at the stakes by thousands of angry containerlab users.

I'm in the process of a more comprehensive maintenance of Edgeshark and would like to introduce the compose oci:// method as part of it.

I've found an issue with current compose when trying to work with deployer-supplied envvar overrides that is now fixed upstream but not yet released. This isn't a blocker, but cripples at the moment the fuller potential of oci artefact deployments.

These past weeks I made full headway through Edgeshark's core dependencies, especially the non-straightforward migration from the EOL Docker client SDK to it's successor Moby client SDK. The most important benefit is much reduced CVE noise, that is, CVEs targeting Docker The Demon and not the SDK. Another benefit is finally semver instead of calver.

So, things are moving forward.

[thomaseizinger]

Thank you for the update! Looking forward to the improved version :)