denzp/rust-buildkit

BuildKit integration for Rust

BuildKit binding for Rust

Project structure

This repository contains three important building blocks to implement BuildKit frontends in Rust:

• buildkit-llb - high-level API to create BuildKit LLB graphs,

• buildkit-frontend - foundation and utilities for BuildKit frontends,

• buildkit-proto - low-level protobuf interfaces to BuildKit.

rust-buildkit's Issues

Repo doesn't compile out-of-box

I've noticed that the Cargo.lock file is gitignored in this repo, and unfortunately the repo doesn't compile of out the box anymore due to a change in indexmap::IndexSet (which now requires 2 type arguments). Would you be open to adding a Cargo.lock file to make the repo build reproducible?

Project status?

Hello! We are interested in using this buildkit library for writing our own build system. We would like to know about the status of this project. It seems to be dead for around 2 years now.

Will this library still be maintained or not?

What is OutputRef?

Would it be possible to a add some documentation about OutputRef? I see it is a newtype-struct for String, bue I'm not sure what that String represents. Is it a serialized form of LLB?

forking rust-buildkit

hi @denzp! i wanted to make you aware that i have temporarily forked your project at https://github.com/edrevo/dockerfile-plus i would love to contribute back the (admittedly small) changes i have made to the projects if that's OK, and depend upon an official version of buildkit-proto and buildkit-llb

i am not a lawyer, so if i did anything wrong while forking your code, please do let me know and i'll fix it right away.

cheers and thanks for the awesome project!

Duplicated input indices

I am by no means an expert and just started reading into BuildKit and the inner workings of LLB but this looks not quite right:

The input is listed twice with the same index. In this specific case (buildkit-llb scratch example from current master) it doesn't cause any issues due to the equal digest but in the case of the highly-parallel example two different digests are occupying the same input index. I noticed some funky business with the index matching going on earlier and this is likely the cause for that.

Might be worth a look :)

{
  "Op": {
    "inputs": [
      {
        "digest": "sha256:4db4c9e0ad6c39235aa82237c23fc85ce11c5e1069cd86442c69019b66906f3b",
        "index": 0
      },
      {
        "digest": "sha256:4db4c9e0ad6c39235aa82237c23fc85ce11c5e1069cd86442c69019b66906f3b",
        "index": 0
      }
    ],
    "Op": {
      "file": {
        "actions": [
          {
            "input": 1,
            "secondaryInput": 0,
            "output": 0,
            "Action": {
              "copy": {
                "src": "/file0",
                "dest": "/file1",
                "mode": -1,
                "timestamp": -1
              }
            }
          },
          {
            "input": 2,
            "secondaryInput": 2,
            "output": 1,
            "Action": {
              "copy": {
                "src": "/file0",
                "dest": "/file2",
                "mode": -1,
                "timestamp": -1
              }
            }
          }
        ]
      }
    }
  },
  "Digest": "sha256:2debf72ab9472756432c19c2dd418b46b394ee8e5877ab8feae84bdd4da3ff14",
  "OpMetadata": {
    "description": {
      "llb.customname": "do multiple file system manipulations"
    },
    "caps": {
      "file.base": true
    }
  }
}

Command that produced this output:

cargo run --example=scratch | buildctl debug dump-llb | jq . | less