I'm working to get Buttercup running locally with
sudo apt update
sudo apt install -y make curl git
git clone --recurse-submodules https://github.com/trailofbits/buttercup.git
cd buttercup
make setup-local
make deploy
make send-libpng-task
I can't get make deploy to finish successfully without editing deployment/k8s/charts/merger-bot/values.yaml to have a cpu: 4000m limit instead of cpu: 8000m even on a system with 20 cores.
It inconsistently works to get through the fuzzing step. It consistently does not work to start the patching step. Running make undeploy then later (like the next day) make deploy often doesn't work. Sometimes make deploy will finish after a make undeploy but a subsequent make send-libpng-task or the equivalent using the web UI will fail with a 500 error (and no detail as to the actual server error in Signoz-UI). I've had better luck tearing down and recreating my local VMs to get an instance of buttercup running again.
Eventually if the make web-ui is stopped or if the UI server process fails for some reason, any existing browser with the UI open will show the libpng task as if it actually finished, even though it doesn't look like in the logs as that it did complete.
I've seen errors logged in Signoz-UI about an incorrect Docker API:
Error response from daemon: client version 1.52 is too new . Maximum supported API version is 1.43
Though I can't reproduce this anymore. When I received this error, it appeared to be related to the patcher not working. I thought I needed a Docker old enough to use API v1.43 (like Docker v24.x), but I see that internal Dockerfile are using Docker v29, so I'm not sure that actually helped.
I pretty consistently see errors like this in Signoz-UI, but I'm not sure if they are actually stopping anything from working:
2025-11-21 14:27:22,189 - opentelemetry.exporter.otlp.proto.grpc.exporter - ERROR - Failed to export logs to buttercup-signoz-otel-collector:4317, error code: StatusCode.UNAVAILABLE
I've tried from both Ubuntu 24.04 and 22.04 VM hosts as well as in WSL with Ubuntu 24.04 and 22.04. Though WSL may have its own issues as I did receive warnings suggesting I use Docker Desktop instead of WSL.
I see in the logs and Makefile & scripts that the Docker containers are made locally each time I run make deploy. Are tested versions of these containers available to pull instead of building local? I did a search on https://hub.docker.com/ for buttercup and Trail of Bits, but I didn't find any.
I imagine I'm missing something important in the initial configuration or in the systems where I'm trying to deploy buttercup, but I haven't been able to find what that may be, so I was hoping to start with a known working set of containers.
I know this is more of a support request than a bug report, so if there's a better place for me to reach out for support, please point me there and close this ticket.
I'm working to get Buttercup running locally with
I can't get
make deployto finish successfully without editingdeployment/k8s/charts/merger-bot/values.yamlto have acpu: 4000mlimit instead ofcpu: 8000meven on a system with 20 cores.It inconsistently works to get through the fuzzing step. It consistently does not work to start the patching step. Running
make undeploythen later (like the next day)make deployoften doesn't work. Sometimesmake deploywill finish after amake undeploybut a subsequentmake send-libpng-taskor the equivalent using the web UI will fail with a 500 error (and no detail as to the actual server error in Signoz-UI). I've had better luck tearing down and recreating my local VMs to get an instance of buttercup running again.Eventually if the
make web-uiis stopped or if the UI server process fails for some reason, any existing browser with the UI open will show the libpng task as if it actually finished, even though it doesn't look like in the logs as that it did complete.I've seen errors logged in Signoz-UI about an incorrect Docker API:
Error response from daemon: client version 1.52 is too new . Maximum supported API version is 1.43Though I can't reproduce this anymore. When I received this error, it appeared to be related to the patcher not working. I thought I needed a Docker old enough to use API v1.43 (like Docker v24.x), but I see that internal Dockerfile are using Docker v29, so I'm not sure that actually helped.
I pretty consistently see errors like this in Signoz-UI, but I'm not sure if they are actually stopping anything from working:
2025-11-21 14:27:22,189 - opentelemetry.exporter.otlp.proto.grpc.exporter - ERROR - Failed to export logs to buttercup-signoz-otel-collector:4317, error code: StatusCode.UNAVAILABLEI've tried from both Ubuntu 24.04 and 22.04 VM hosts as well as in WSL with Ubuntu 24.04 and 22.04. Though WSL may have its own issues as I did receive warnings suggesting I use Docker Desktop instead of WSL.
I see in the logs and Makefile & scripts that the Docker containers are made locally each time I run
make deploy. Are tested versions of these containers available to pull instead of building local? I did a search on https://hub.docker.com/ for buttercup and Trail of Bits, but I didn't find any.I imagine I'm missing something important in the initial configuration or in the systems where I'm trying to deploy buttercup, but I haven't been able to find what that may be, so I was hoping to start with a known working set of containers.
I know this is more of a support request than a bug report, so if there's a better place for me to reach out for support, please point me there and close this ticket.