dinker
dockerfile-rails
dinker | dockerfile-rails | |
---|---|---|
2 | 5 | |
12 | 439 | |
- | 3.0% | |
10.0 | 8.9 | |
3 months ago | 6 days ago | |
Go | Dockerfile | |
ISC License | 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.
dinker
-
Crafting container images without Dockerfiles
(Self plug) I had the same thoughts as the author, and made this: https://github.com/andrewbaxter/dinker . Like stated in the article, if you're doing rust or go all you want is to dump the binary in the image. There's no reason to do the build inside the docker vm in that case, and it's super fast, and only uses dumb filesystem access - no daemons like docker, weird wip container managers like buildah, etc.
-
Rails on Docker · Fly
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.
dockerfile-rails
-
Rails 7.1: Dockerfiles, BYO Authentication, More Async Queries, and More
If you want to automatically generate Dockerfiles for more versions of Rails (not just the latest) that detect OS packages that need to be installed from gems present in your Gemfile, check out https://github.com/fly-apps/dockerfile-rails
You can install it in your rails app by running:
1. bundle add dockerfile-rails
2. rails g dockerfile
-
Around the World with SQLite3 and Rsync
> I felt bad
Don't. I can honestly say that I didn't write this post targeting HN. I'll go further... this post wasn't meant for people who are unlikely to use https://github.com/fly-apps/dockerfile-rails#overview. I recently added some features to that gem whose usage may not be intuitively obvious. I wrote this post to explain some of the motivation for those features.
I don't know how to mark posts as not intended for HN (and truth be told, if there was such a feature, I'd be inclined to overuse it). I don't know where else I should have posted this content, but I'm not sure I would be inclined to move it. In any case, this post, as written, serves a purpose for me. Somebody not you and not me felt it belonged here. We can both second guess that decision. Either way, there is no reason for either of us to feel bad.
-
Rapid growth, lessons learned and improvements at Fly.io
Did you try migrating with this guide? https://fly.io/docs/rails/getting-started/migrate-from-herok...
The issues you ran into with older versions of Rails was probably because the Dockerfile that `fly launch` generated was for new versions of Rails. We switched to https://github.com/rubys/dockerfile-rails to streamline Dockerfile generation and support older versions of Rails.
If you try it again and run into issues you can open an issue at https://github.com/rubys/dockerfile-rails/issues or post in https://community.fly.io and somebody will help get that sorted out.
The more versions of Rails we can deploy the better!
-
Rails on Docker · Fly
At the moment Rails is focused on simplicity/readability. I've got a gem that I'm proposing (and DHH is evaluating) that adds caching as an option: https://github.com/rubys/dockerfile-rails#overview
-
Rails on Docker
even though the article does not go deep into multistage builds Fly.io does provide cookbooks and even a link to a Rails generator there.
What are some alternatives?
buildah - A tool that facilitates building OCI images.
docked - Running Rails from Docker for easy start to development
manifest-tool - Command line tool to create and query container image manifest list/indexes
docker-projects
bazel-nix-example
deploy-cloud-functions - A GitHub Action that deploys source code to Google Cloud Functions.
lamby - 🐑🛤 Simple Rails & AWS Lambda Integration
libaws - aws should be easy
nix2container - An archive-less dockerTools.buildImage implementation
cruftspy - Detect unnecessary files in Docker images
rules_nixpkgs - Rules for importing Nixpkgs packages into Bazel.