ktock/buildg

Interactive debugger for Dockerfile, with support for IDEs (VS Code, Emacs, Neovim, etc.)

buildg's Issues

containerize buildg

Based on the comments in issue #45 by @ktock, we decided that it'd be better to containerize the build tool to support macOS or any other alternatives.

#45 (comment)

add macOS support

We (w/@Dentrax) can use os-matrix to build an artifact suitable for macOS, is it possible to build a buildg tool for macOS from a technical standpoint?

jobs:
  build:
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        os: [macos-latest, ubuntu-latest, windows-latest]

Request: make binary artifacts to be statically linked

Context: lima-vm/alpine-lima#77 (comment)

First line on Dockerfile's Syntax seems to terminate debugging session instantly

Thank you for this cool OpenSource project!

I have an issue, when debugging my Dockerfiles, which start using Docker BuildKit's Dockerfile-Syntax declarations like this one.

When I remove this first line "# syntax = docker/dockerfile:1.4.3", the debugger IS working perfectly. Having this first line included results in weird output of it:

The debugger seems to not understand this line and terminates directly — even when this image is present locally in my repository.

Cryptic error message adding tarball "Breakpoint[on-fail]: caught error Error processing tar file(exit status 3): No help topic for '/'"

I'm trying to debug a Dockerfile that's failing with standard buildx. I get an error with buildg before the line that fails with buildx.

#7 68.21 Certificate added: C=CN, O="iTrusChina Co.,Ltd.", CN=vTrus Root CA
#7 68.21 140 new root certificates were added to your trust store.
#7 68.21 Import process completed.
#7 68.21 Done
#7 68.21 done.
#7 68.24 Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.10+dfsg-1+b1) ...
#7 DONE 68.4s

#8 [inst 1/6] RUN mkdir /build
#8 DONE 0.2s

#9 [inst 2/6] ADD Quartus-lite-17.0.2.602-linux.tar /build
Breakpoint[on-fail]: caught error Error processing tar file(exit status 3): No help topic for '/'

Filename: "Dockerfile"
     12| FROM pre-inst AS inst
     13| 
     14| RUN mkdir /build
 =>  15| ADD Quartus-lite-17.0.2.602-linux.tar /build
     16| ADD "https://ftp-osl.osuosl.org/pub/libpng/src/libpng12/libpng-1.2.59.tar.xz" \
     17|     /build
     18| 

I can add more context but I don't see anything more that seems relevant. As the title says, the error message is extremely cryptic as far as I'm concerned and I don't even know where to start with this. Again, the Dockerfile gets past this point with standard buildx.

The two commands that I run are: nerdctl builder debug . and docker build -f Dockerfile -t ${CONTAINER_AUTH} ..