compose2nix icon indicating copy to clipboard operation
compose2nix copied to clipboard

A tool to automatically generate a NixOS config from a Docker Compose project.

Results 8 compose2nix issues
Sort by recently updated
recently updated
newest added

Hi! `compose2nix` really is awesome, and exceeds all of my expectations! As I’m migrating a bunch of Docker Compose definitions, I was wondering if it would be wise to add...

feature

Fix an issue where special characters were not properly escaped in template, leading to Nix parsing errors. Tests have been checked and pass. Test data has been written from the...

This behavior would be controlled by a flag with default = `false`. Directory structure: ``` $ ls service-a.nix service-b.nix volumes.nix networks.nix default.nix ``` Where `default.nix` looks something like this: ```nix...

feature

We would need to use [`docker cp`](https://docs.docker.com/reference/cli/docker/container/cp/#examples) to copy applicable secrets into the container. The reason is that that this is a **runtime** feature and therefore requires running commands after...

feature

Here: https://docs.docker.com/compose/compose-file/build/ For a Git based build context, the generated Nix derivation needs to: 1. Clone the repo (with a correct hash) 2. Build a Docker imagee This can be...

feature

Hi, first of all, thanks for the awesome tool. I really want to use it, but I noticed that the 'user' statement is not listed as a supported feature for...

Look at this for a usage example: https://github.com/docker/compose/blob/main/cmd/compose/compose.go

We can use Compose labels to control how env files are included at a per-service level: Example: ```yaml services: abc: env_file: - ./secret.env labels: - "compose2nix.settings.envFilesOnly=true" ```

feature