nectar
swarm-cronjob
| nectar | swarm-cronjob | |
|---|---|---|
| 1 | 5 | |
| 7 | 707 | |
| - | - | |
| 0.0 | 7.9 | |
| over 2 years ago | 5 days ago | |
| Go | Go | |
| - | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nectar
-
Deep Dive: Nectar
If you’re curious about it, you can already install it and start experimenting with it. Currently, Nectar encompasses an alpha version of a Linux-based client that connects to Swarm. The latest release and installation instructions are available on their GitHub page. In case you get stuck, the team is reachable on Discord, Telegram and Twitter.
swarm-cronjob
-
Efficiency between docker restart and container with sleep
Anything from simple crontab entry to something like this: https://crazymax.dev/swarm-cronjob/
-
How do you evaluate if a tool is trustworthy?
So, I found a really nice little tool that solves a problem I have in a really nice way. Specifically, cron jobs on Docker Swarm. This project: https://github.com/crazy-max/swarm-cronjob It uses labels on your services to schedule jobs. Thus it needs access to the docker api, and all the security concerns that go along with it...
-
Rancher Desktop, a Docker Desktop Replacement
As i said, if it's not exposed to the outside world and doesn't work with untrusted data, that claim is not entirely valid.
Imagine something like this getting abandoned, or someone running a year old version of it: https://github.com/crazy-max/swarm-cronjob/blob/master/READM...
Its only job is to run containers on a particular schedule, no more no less. There are very few attack vectors for something like that, considering that it doesn't talk to the outside world, nor processes any user input data.
Then again, it's not my job to pass judgement on situations like that, merely acknowledge that they exist and therefore the consequences of those suddenly breaking cannot be ignored.
-
Docker Swarm cron job manager
I also found swarm-cronjob and ofelia both seems promising. BUT , I really like the idea of an interface to watch log files etc.
What are some alternatives?
bee - Bee is a Swarm client implemented in Go. It’s the basic building block for the Swarm network: a private; decentralized; and self-sustaining network for permissionless publishing and access to your (application) data.
ofelia - A docker job scheduler (aka. crontab for docker)
swarm-scheduler - A distributed scheduler for docker swarm mode using Compose and Cron
Airflow - Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
Diun - Receive notifications when an image is updated on a Docker registry
k3s - Lightweight Kubernetes
longhorn - Cloud-Native distributed storage built on and for Kubernetes
rancher - Complete container management platform
rd - Container Management and Kubernetes on the Desktop
Moby - The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
hub-feedback - Feedback and bug reports for the Docker Hub