From 2e4b1f85eef04c0abd83f5f47e1aa93c8ea84cb9 Mon Sep 17 00:00:00 2001
From: Vincent Ambo <tazjin@google.com>
Date: Tue, 30 Jul 2019 23:55:28 +0100
Subject: [PATCH] fix(nix): Add empty image config to allow k8s usage

Introduce an empty runtime configuration object in each built layer.

This is required because Kubernetes expects the configuration to be
present (even if it's just empty values).

Providing an empty configuration will make Docker's API return a full
configuration struct with default (i.e. empty) values rather than
`null`, which works for Kubernetes.

This fixes issue #1. See the issue for additional details.
---
 tools/nixery/build-registry-image.nix | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/tools/nixery/build-registry-image.nix b/tools/nixery/build-registry-image.nix
index 25d1f59e7..0d61f3b71 100644
--- a/tools/nixery/build-registry-image.nix
+++ b/tools/nixery/build-registry-image.nix
@@ -133,6 +133,8 @@ let
     os = "linux";
     rootfs.type = "layers";
     rootfs.diff_ids = map (layer: "sha256:${layer.sha256}") allLayers;
+    # Required to let Kubernetes import Nixery images
+    config = {};
   };
   configJson = writeText "${baseName}-config.json" (builtins.toJSON config);
   configMetadata = with builtins; fromJSON (readFile (runCommand "config-meta" {