skopeo VS Zabbix

I believe skopeo should allow you to: https://github.com/containers/skopeo

I decided to go searching for an alternative means to pull a docker image. In my search I discovered Skopeo, an alternative method to download Docker images that proved to be surprisingly effective. It not only downloaded the image faster, it also allowed me to save my image in a tar file, which means you can pull an image on one system and share that image to another system, loading it easily to docker instance on that system. This can be very beneficial if you have multiple systems and don't want to download an image multiple times.

But I'd suggest looking into if it's solved by other tools already, like regclient/regclient and their regsync features or something like containers/skopeo.

Have a use case where we have a CLI (built with cobra) for our dev teams which can execute common tasks. One of those tasks we want to implement is to copy docker images from the internet to our internal registry. A tool such as skopeo can do this and much more. Instead of essentially re-writing the functionality directly into our CLI we'd like to embed it. This would also negate the need for the dev teams to manage multiple CLI tools.

Self hoisting here, I put this together to make it easier to generate single (extra) layer docker images without needing a docker agent, capabilities, chroot, etc: https://github.com/andrewbaxter/dinker

Caveat: it doesn't work on Fly.io. They seem to be having some issue with OCI manifests: https://github.com/containers/skopeo/issues/1881 . They're also having issues with new docker versions pushing from CI: https://community.fly.io/t/deploying-to-fly-via-github-actio... ... the timing of this post seems weird.

FWIW the article says

> create a Docker image, also known as an OCI image

I don't think this is quite right. From my investigation, Docker and OCI images are basically content addressed trees, starting with a root manifest that points to other files and their hashes (root -> images -> layers -> layer configs + files). The OCI manifests and configs are separate to Docker manifests and configs and basically Docker will support both side by side.

skopeo is another tool worth looking into. we've started deploying amd and arm nodes into our k8s clusters, and this tool was incredibly easy to build around for getting multi-arch images into our container registry.

I would use skopeo, the tool is quite handy for working with remote images. https://github.com/containers/skopeo

Using distroless images not only reduces the size of the container image it also reduces the surface attack. The need for container image signing is because even with the distroless images there is a chance of facing some security threats such as receiving a malicious image. We can use cosign or skopeo for container signing and verifying. You can read more about securing containers with Cosign and Distroless Images in this blog.

Look at using tools like skopeo or crane

You could try some commandline tool like skopeo to fetch the image tags regularly and do some shell magic to notify you on any change you want

A powerful open source SolarWinds alternative that combines modern features with enterprise-grade scalability. Zabbix provides comprehensive monitoring capabilities while maintaining the flexibility of an open-source solution.

Zabbix is an open-source enterprise-level monitoring solution that can be considered a robust prometheus alternative.

Zabbix is an open source software that monitors numerous parameters of a network and the health and integrity of servers, virtual machines, applications, services, databases, websites, the cloud and more. Zabbix uses a flexible notification mechanism that allows users to configure email-based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualization features based on the stored data. This makes Zabbix ideal for capacity planning.

GitHub: Zabbix GitHub Repository

Zabbix

Zabbix is a comprehensive open-source monitoring solution designed for real-time monitoring and management of various network components, such as servers, networks, and applications. It excels in data collection and processing, enabling proactive monitoring for early issue detection and resolution.

The PHP core package is offered as pre-compiled binary via Ports packages system. In addition, important softwares such as extensions, Composer and PECL libraries are available. So are frameworks such as NextCloud and Zabbix.

Prometheus is a great way to go, however you need to invest time in writing all the alerts. This was a daunting task for us, because we have too many vendors and device types.. we instead went with zabbix, which is a free open source platform similar to Orion. Quite easy to setup. All the device templates for monitoring alerting are provided by the community. There is a grafana plugin which integrates with Zabbix, so you can build beautiful dashboards in grafana while using the polling and alerting logic in zabbix. You can also use grafana OnCall via a zabbix integration. Phase1: You could move to zabbix. Realize cost savings without investing time. Phase2: learn and work on moving things to Prometheus slowly. edit: added links and some rewording

Setup Zabbix (https://www.zabbix.com/) and use SNMP (search for a template for your switches, chances are someone has created one) to pull throughput data from the switchport your proxies are connected to. This will graph them for you on a continual basis, you can then setup some triggers (alerts) that will flag over-utilization (say >80Mbps) for you, can generate an email or SMS alert based on that or just see it in the dashboard.