Question 1

Should I use Nixery or write Dockerfiles for my containers?

Accepted Answer

Use Nixery if you're already using Nix and want declarative, reproducible images with efficient caching. Dockerfiles offer more control for custom build steps and are better for teams not using Nix.

Question 2

How to set up a private Nixery instance with AWS S3?

Accepted Answer

Configure environment variables like S3_BUCKET, AWS_REGION, and optionally S3_ACCESS_KEY, then deploy Nixery as a service. Ensure the S3 bucket is accessible and supports signed URLs if needed for security.

Question 3

Can Nixery handle custom entry points or commands in images?

Accepted Answer

Nixery focuses on package inclusion; for custom commands, you may need to use meta-packages like 'shell' or overlay Nix packages to define behavior, as it doesn't support arbitrary Dockerfile instructions.

Question 4

What are the performance implications of Nixery's on-demand building?

Accepted Answer

First-time builds can be slow due to Nix evaluation and package fetching, but smart caching minimizes latency for subsequent requests. Build times vary based on package complexity and network conditions.

Question 5

Is Nixery suitable for production environments with high traffic?

Accepted Answer

Yes, with proper scaling of the registry service and storage backend (e.g., S3 or GCS). However, on-demand builds might not be ideal for latency-sensitive apps; consider pre-building critical images.

Question 6

How does Nixery's layering strategy compare to Docker's layer caching?

Accepted Answer

Nixery's layering is based on Nix derivations, optimizing for dependency sharing across images, while Docker's is file-based. This can lead to better cache hits in multi-image environments but requires Nix familiarity.

Nixery

What is Nixery?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions