I'm not sure what I need to do to get started. Do I have to clone the repo somewhere? Do I have to "install" dockerfile-plus so docker will recognize the 'syntax' command? Please elaborate on how to get dockerfile-plus properly build/configured so the rest of the Getting Started example works.

Thanks.

I get the following error when the 'Dockerfile.common' is not in the same directory.

failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: rpc error: code = Code(128) desc = Could not read file " ../../../mbKinDyn-algos/docker.requirements". Remember that the file path is relative to the build context, not the Dockerfile path.

I also tried using an absolute path and got the same error.

The third test was to make the CWD a parent of both the Dockerfile folder and the 'docker.requirements' folder and then I used a relative path to both the Dockerfile and 'docker.requirements' from the parent folder. This produced the same error.

I have multiple git repositories that are related to the Docker container that I'm building. Each repository has a 'docker.requirements' file that documents the dependencies that it needs backed into the docker image/container. So, I need the ability to keep these INSERT+ files in locations other than the main Dockerfile.

Thoughts?

docker build works great

docker-compose up dies with the error

dockerfile parse error line 2: unknown instruction: INCLUDE+

My a.Dockerfile looks like:

# syntax = edrevo/dockerfile-plus
INCLUDE+ /Dockerfile

I get this error:

failed to solve with frontend dockerfile.v0: failed to create LLB definition: dockerfile parse error line 3: unknown instruction: INCLUDE+

Here is the version of Docker:

Client:
 Version:           20.[10]
 API version:       1.41
 Go version:        go1.16
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server:
 Engine:
  Version:          20.10.11+azure-3
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.12
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.12+azure-2
 runc:
  Version:          1.0.3

I have set the environment variables:

    env:
      DOCKER_BUILDKIT: 1
      COMPOSE_DOCKER_CLI_BUILD: 1

I was able to build this repo in raspberry pi (arm64v8) with minor changes in the Dockerfile. However when I used the built output in another dockerfile (use INCLUDE+) it would fail with “failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: exit code: 1”. Do you have any idea why it would fail?

The changes I made in this repo:

1. Use arm64v8/rust as the base image
2. Change the target to aarch64-unknown-Linux-gnu

I really like the INCLUDE+ instruction, since it allows to avoid code duplication. The only problem I encountered was using multiple levels of INCLUDE+ (i.e. including a file using INCLUDE+ as well).

Not sure if i am doing something wrong, there is a limitation or it just is not implemented. I think it is just not considered in the implementation (i.e. missing recursive call on the included file) but i could be wrong, since i do not know rust.

My files look like this:

Dockerfile.A:

# syntax = edrevo/dockerfile-plus
FROM alpine
RUN echo ">A"
INCLUDE+ Dockerfile.A2
RUN echo "<A"

Dockerfile.A2:

# syntax = edrevo/dockerfile-plus
RUN echo ">A2"
INCLUDE+ Dockerfile.A3
RUN echo "<A2"

Dockerfile.A3:

# syntax = edrevo/dockerfile-plus
RUN echo ">A3"
RUN echo "<A3"

Here you can find the files: https://gitlab.com/barcode/test/-/tree/ci/multi_level_include

The build output is here: https://gitlab.com/barcode/test/-/jobs/1214501093

So is this a problem with my files or is it something else?

When we do

# syntax = edrevo/dockerfile-plus

in a dockerfile, a docker container is launched from edrevo/dockerfile-plus image which contains the grpc server.

Is there any way to get logs from this frontend container for the purpose of debugging the build? This frontend container is short lived, so is there any way on getting the logs from this container?

I can see that some logs are being written to stderr in here https://github.com/edrevo/dockerfile-plus/blob/master/dockerfile-plus/src/dockerfile_frontend.rs#L111

Is there any way of seeing these logs? Even just being able to view stderr from the frontend container would suffice.

I'm using INCLUDE+ to include a Dockerfile that includes heredocs, which means that I'm setting DOCKER_BUILDKIT=1 before invoking docker build. I'm getting the same error as when I run the included Dockerfile without setting DOCKER_BUILDKIT: namely, docker build is choking on the contents of the heredoc because it's trying to parse them as if they're part of the Dockerfile.

My best guess as to what's going on is that heredocs are processed at some early stage of Dockerfile parsing, and the INCLUDE+ directive is getting parsed later -- so when it interpolates the contents of the included file, they're not being parsed correctly. Not being expert in ruby OR Docker, that's about as far as I can get in tracking down the problem.

hello

when trying to use INCLUDE+ syntax I am getting the error below

PS C:\work\bitbucket\devops\Docker> docker build -f ./qa-windows/Dockerfile -t win_diab . Sending build context to Docker daemon 58.37kB Error response from daemon: dockerfile parse error line 66: unknown instruction: INCLUDE+

OS: windows Docker version : 20.10.17, build 100c701

This was tested on a

OS: Raspbian GNU/Linux 11 (bullseye) armv7l
Host: Raspberry Pi 4 Model B Rev 1.2
Kernel: 5.15.32-v7l+
Uptime: 1 hour, 49 mins
Packages: 651 (dpkg)
Shell: bash 5.1.4
Terminal: /dev/pts/0
CPU: BCM2711 (4) @ 1.500GHz
Memory: 127MiB / 3838MiB

with Docker 20.10.14

which causes this:

$ DOCKER_BUILDKIT=1 COMPOSE_DOCKER_CLI_BUILD=1 docker build -t ghcr.io/tbrodbeck/qoffee-maker-arm:0.1.1 -f DockerfileArm . && docker run --name qoffeeMaker --rm -itp 8887:8887 --env-file .env ghcr.io/tbrodbeck/qoffee-maker-arm:0.1.1
[+] Building 2.8s (3/3) FINISHED
 => [internal] load build definition from DockerfileArm                                                                                                                                                    0.2s
 => => transferring dockerfile: 575B                                                                                                                                                                       0.0s
 => [internal] load .dockerignore                                                                                                                                                                          0.1s
 => => transferring context: 90B                                                                                                                                                                           0.0s
 => ERROR resolve image config for docker.io/edrevo/dockerfile-plus:latest                                                                                                                                 1.5s
------
 > resolve image config for docker.io/edrevo/dockerfile-plus:latest:
------
failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: no match for platform in manifest sha256:d234bd015db8acef1e628e012ea8815f6bf5ece61c7bf87d741c466919dd4e66: not found

This extension is awesome! But it causes some ugliness in VS code like:

Since VS code is one of the most used editors - does anyone know a solution or workaround to this?

I'm building on an embedded system, using Visual Studio Code's remote build facility which works over SSH. When I try to use dockerfile-plus I get the following:

=> [internal] load build definition from Dockerfile                                                                                                                                                                                          0.0s
 => => transferring dockerfile: 1.19kB                                                                                                                                                                                                        0.0s
 => [internal] load .dockerignore                                                                                                                                                                                                             0.1s
 => => transferring context: 34B                                                                                                                                                                                                              0.0s
 => ERROR resolve image config for docker.io/edrevo/dockerfile-plus:latest                                                                                                                                                                    0.4s
------
 > resolve image config for docker.io/edrevo/dockerfile-plus:latest:
------
failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: rpc error: code = Unknown desc = error getting credentials - err: exit status 1, out: `Cannot autolaunch D-Bus without X11 $DISPLAY`

I presume this is because it is trying to use the new fancy output format which won't work over SSH, is that correct?