dotfiles VS buildkit

You can take a look at my nvim configs here. I’m a Ruby dev, and like to poke around with my nvim configuration as a hobby. I’m pretty happy with where I have it, although it’s always a work in progress.

Not an answer to you're question, but do youferl safe doing (https://github.com/jchilders/dotfiles/blob/main/Makefile#L34)

> sudo curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/in... | /bin/bash

piping the output of a curl command to sh without first checking the sha256 of the file you just got?

That was my impression. I’ve been doing this for years with Ruby, tmux, and some custom zsh widgets.

https://github.com/jchilders/dotfiles

These are my dotfiles. I'm a Rails dev, and I'm using neovim nightly + solargraph. Here's a partial screenshot of something I'm working on right now showing a rubocop warning for the current line. The window showing it is being provided by lspsaga.

I know people like playing with neovim’s terminal buffers these days, but in the spirit of “use the right right tool for the job”, I gave up on using nvim for things like this and went back to tmux. I have a mapping I use that runs rspec in the adjacent pane. It uses tmux’s send-keys to do the right thing. You could do the same thing, only instead of executing rspec, you would send it your tail command.

> We are uding docker-in-docker at the moment

You can also run a "less privileged" container with all the features of Docker by using rootless buildkit in Kubernetes. Here are some examples:

https://github.com/moby/buildkit/tree/master/examples/kubern...

https://github.com/moby/buildkit/blob/master/examples/kubern...

It's also possible to run dedicated buildkitd workers and connect to them remotely.

- BuildOp evaluates its input as additional LLB operations to add to the graph to allow for dynamic build graphs (also unused in the Dockerfile frontend)

With the Dockerfile Explorer, we run the Dockerfile frontend[1] that BuildKit uses inside of WASM to parse and produce the LLB output locally in your browser. We then embed the Monaco Editor so that you can change your Dockerfile to see how it impacts the LLB output that BuildKit will use to build your Docker image.

You can see a quick video and read more details on how it all works here: https://depot.dev/blog/dockerfile-explorer.

We'd love any feedback or ideas folks would like around this type of tool!

[0] https://github.com/moby/buildkit#exploring-llb

Now since Kubernetes works off of containerd I'll be taking a different approach on handling container builds by using nerdctl and the buildkit that comes bundled with it. I'll do this on the amd64 control plane node since it's beefier than my Raspberry Pi workers for handling builds and build related services. Go ahead and download and unpack the latest nerdctl release as of writing (make sure to check the release page in case there's a new one):

There's a 2-year-old moby/buildkit GitHub issue about frequent build cache misses when using the BuildKit docker-container driver and multi-stage builds. Anyone else in this sub run into this problem and/or have reasonable workarounds? It seems like something that should come up pretty often.

A couple months ago I encountered a bug in buildkit - when enabling OpenTelemetry tracing, we got occasional panics. With a bit of investigation, we found the cause, fixed and tested in our fork and internal deployments, and pushed to upstream.

I do some search in the internet and there seems to be no good solution, so I just create a feature request: https://github.com/moby/buildkit/issues/3859

Yeah, only Linux containers at the moment, BuildKit is the way we are constructing pipelines and doing caching. Split on if we will support non-linux hosts, but definitely want to find a good solution to not doing Docker-in-Docker.

Relevant issues are https://github.com/moby/buildkit/issues/3011 and https://github.com/moby/buildkit/issues/1512.