How to set up Dockly build cache in a CI/CD pipeline?

Define a build_cache block in your DSL with S3 bucket details and hash commands. Dockly will automatically upload cache after builds and download it in subsequent runs to skip redundant steps, speeding up pipelines.

Can Dockly generate Kubernetes manifests instead of Foreman scripts?

No, Dockly is designed for system packages with Foreman export scripts. For Kubernetes, you'd need to use additional tools or customize the output, as it doesn't natively support container orchestration.

Dockly vs Docker Compose for deployment: which should I use?

Dockly is for creating packaged, production-ready artifacts with system integration, while Docker Compose is better for local development and multi-container app definitions. Use Dockly for server deployments, Docker Compose for development.

How does Dockly handle secrets like registry passwords?

Dockly supports environment variables (e.g., ENV['DOCKER_REGISTRY_PASSWORD']) for registry authentication, but you must manage secrets externally, which adds complexity in secure environments.

Does Dockly support building Docker images for ARM architectures?

The README doesn't mention multi-arch support; it defaults to x86_64 for packages. You may need to extend or use other tools for ARM compatibility.

What are good alternatives to Dockly for Ruby projects?

Consider tools like FPM for package creation with custom scripts, or Packer for image building. Dockly is unique for its integrated Ruby DSL but is niche for AWS-centric Ruby teams.

Open-Awesome

Dockly

MITRubyv3.0.5

A Ruby gem providing a DSL to build and package Docker images into deployable artifacts like Debian packages.

GitHub

228 stars10 forks0 contributors

What is Dockly?

Dockly is a Ruby gem that simplifies packaging applications into production-ready Docker images and deployable system packages like Debian packages (deb) or RPMs. It provides a declarative domain-specific language (DSL) to define build pipelines, manage dependencies, and create consistent, automated deployment artifacts. The tool aims to reduce the complexity of application packaging by abstracting the intricacies of Docker and system packaging.

Target Audience

DevOps engineers and Ruby developers who need to automate and standardize the creation of Docker-based deployment packages for production environments. It is particularly suited for teams managing deployments across multiple servers or cloud instances.

Value Proposition

Developers choose Dockly for its integrated DSL that unifies Docker image creation, build cache management, and system package generation into a single workflow. Its unique selling point is the ability to create Debian or RPM packages that bundle Docker images and optional Foreman startup scripts, ensuring reproducible and automated deployments with support for AWS S3 caching and ECR registry integration.

Overview

DSL and Gem for building ready-to-launch Docker images

Use Cases

Best For

Automating the creation of Debian or RPM packages that include Docker images for consistent server deployments.
Managing build cache artifacts in AWS S3 to speed up compilation and avoid redundant rebuilds in CI/CD pipelines.
Integrating Docker image builds with AWS ECR or other Docker registries for streamlined container publishing.
Generating Foreman export scripts for process management within packaged applications on Linux systems.
Defining complex Docker build pipelines with a declarative Ruby DSL for teams using Ruby-based tooling.
Packaging applications that require isolated dependencies and process management using Docker and system packages.

Not Ideal For

Teams not using Ruby or AWS services, as Dockly's DSL is Ruby-based and integrates tightly with S3 and ECR.
Projects requiring immediate support for container orchestration like Kubernetes, as Dockly focuses on system packages and Foreman for process management.
Environments that prefer YAML or JSON configuration over a Ruby DSL for infrastructure-as-code.

Pros & Cons

Pros

Declarative Ruby DSL

Provides a clean, Ruby-based DSL to define Docker images and packages, reducing boilerplate and errors compared to manual scripting.

Build Cache Optimization

Integrates with AWS S3 to cache build artifacts, skipping redundant compilations and speeding up CI/CD pipelines, as detailed in the build_cache DSL.

Integrated Registry Support

Automates pushing to Docker registries like AWS ECR with built-in authentication, simplifying deployment workflows.

System Package Generation

Creates Debian or RPM packages that bundle Docker images and Foreman scripts, ensuring consistent deployments across Linux servers.

Cons

AWS Vendor Lock-in

Heavily relies on AWS S3 for caching and ECR for registries; using other clouds requires custom workarounds or missing features.

Complex Toolchain Dependency

Requires setup with Docker, Foreman, AWS CLI, and Ruby, making initial configuration cumbersome for teams not already using this stack.

Limited Ecosystem Support

Focuses on deb/rpm packages and Foreman; lacks native support for modern tools like systemd, Kubernetes, or multi-architecture builds.

Frequently Asked Questions

Related Projects

DockerSlim

Slim(toolkit): Don't change anything in your container image and minify it by up to 30x (and for compiled languages even more) making it secure too! (free and open source)

Stars23,358

Forks839

Last commit1 month ago

BuildKit

concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit

Stars10,148

Forks1,475

Last commit22 hours ago

buildah

A tool that facilitates building OCI images.

Standalone, daemon-less, unprivileged Dockerfile and OCI compatible container image builder.

Stars3,987

Forks232

Last commit2 years ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub