oras
watchtower
oras | watchtower | |
---|---|---|
8 | 215 | |
1,266 | 16,889 | |
3.3% | 1.6% | |
9.3 | 8.2 | |
4 days ago | 11 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
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.
oras
- Distribute Artifacts Across OCI Registries
- OCI image from dockerfile
-
RFC 6920: Naming Things with Hashes
Interesting, I'd not known of this RFC before.
Another example of a content-addressed data store could be OCI registries (more commonly known as container image registries). Using them to store arbitrary artefacts is quite well supported now: https://oras.land/
-
sbcl - require
See https://oras.land/
-
Ocicl – An ASDF system distribution and management tool for Common Lisp
> ... but still only supports one niche operating system.
1. Linux is not a niche in the target market for this project.
2. The project is written in Common Lisp with hard dependencies on SBCL-provided libraries[1], so there's reason to suspect it should work on other OSes supported by SBCL.
3. Sure, the presence of Makefile and sb-posix imply it requires a POSIX compliant OS, but Linux is not the only one that fits the bill.
4. The included Linux-only binary 'oras' is clearly a vendored artifact, not part of this project, and clearly an OCI client. A simple search shows it is indeed cross-platform[2].
Perhaps you should try what almost every Linux user has had to do when encountering software actually built for only one "niche" operating system that they want to use on their OS: look.
1. https://github.com/ocicl/ocicl/blob/170aff0/ocicl.asd#L34
2. https://github.com/oras-project/oras/releases
-
Looking for an artifact store for generic assets, rather than specially-formatted packages or containers. Thinking maybe ORAS, but wondering if there are other options.
oras isn't that unpopular, Helm is using it as an SDK for example. Here are other projects who are using it. https://github.com/oras-project/oras/network/dependents
- OCI Registry as Storage
watchtower
-
My deployment platform is a shell script
Related: https://github.com/containrrr/watchtower
- PSA - Run "docker image prune" once in a while.
-
Roundcube Open-Source Webmail Software Merges with Nextcloud
> if you're using the docker image, upgrades are a breeze. Just bump the tag on the image, redeploy, and you're done.
Or you could just run Watchtower beside it and it will automatically update your docker containers. https://github.com/containrrr/watchtower If you are OK with automated updates.
-
The Curse of Docker
So i primarily use containers on my local machine walled off from the internet, so it's not a big concern for me. Watchtower [1] is popular among home server users too which automatically updates containers to the latest image.
For production uses I think companies generally build their own containers. They would have a common base linux container and build the other containers based off that with a typical CI/CD pipeline. So if glibc is patched, it's probably patched in the base container and the others are then rebuilt. You don't have to patch each container individually, just the base. Production also minimizes the scope of containers with nothing installed except what's necessary so they have few dependencies.
[1] https://github.com/containrrr/watchtower
-
Ask HN: If you were to build a web app today what tech stack would you choose?
You can use Watchtower (https://containrrr.dev/watchtower/) that solves problem of manual pulling on VPS.
-
Running watchtower weekly or whenever new image is available
I checked https://containrrr.dev/watchtower/ and Arguments, but I don't understand where to attach that using portainer.
-
Long Term Ownership of an Event-Driven System
Again, there are options to automate some of the burden here by using tools such as Watchtower.
-
Updating Docker Apps automagically with Watchtower✨🐳
Have you ever deployed a Docker app on a server, but everytime you push a new version of your image to a Docker registry you need to manually restart your app? If you want to automate this restarting, this blog post is for you! I am now going to show you how you can do this with literally 1 simple command using Watchtower!
- Plex Docker Saved me
- Watchtower updates
What are some alternatives?
regclient - Docker and OCI Registry Client in Go and tooling using those libraries.
ouroboros - Automatically update running docker containers with newest available image
containerd - An open and reliable container runtime
Diun - Receive notifications when an image is updated on a Docker registry
distribution - The toolkit to pack, ship, store, and deliver container content
Portainer - Making Docker and Kubernetes management easy.
imgpkg - Store application configuration files in Docker/OCI registries
docker-socket-proxy - Proxy over your Docker socket to restrict which requests it accepts
distribution-spec - OCI Distribution Specification
shepherd - Docker swarm service for automatically updating your services whenever their image is refreshed
quicklisp-https
whats-up-docker - What's up Docker ( aka WUD ) gets you notified when a new version of your Docker Container is available.