Containers on My personal blog

Shipping CPU-optimized Rust binaries in container images

Sun, 28 Jun 2026 00:00:00 +0000

In an earlier post about gguf-runner I made a point that kept nagging at me afterwards.

The point was this: prebuilt binaries are compiled for a conservative baseline so they run everywhere, and if you build locally with target-cpu=native instead, the compiler can light up the SIMD instructions your specific CPU supports. On an AMD Ryzen 7 PRO 8700GE that was worth about +20.8% tokens/sec for LLM inference. Real, measurable, free.

Building containers on Codeberg

Sun, 15 Mar 2026 00:00:00 +0000

I have been moving more and more of my smaller projects over to Codeberg lately.

For plain git hosting and Forgejo based CI, it is a very pleasant setup. The one area where I had to do a bit more work than expected was container builds.

At first glance this looks like it should be boring:

write a Dockerfile
add a CI step
build the image

But on a hosted Codeberg runner this is exactly the type of thing where the defaults are not quite the defaults you may be used to from GitHub Actions or from your own machine.

Reaping some benefits of containerization

Mon, 27 Feb 2023 18:08:54 +0000

We just started the migration and saw some impressive results very early on.

Deployment

We started with some very heavy custom scripting to deploy large composites. These composite container definitions for BW engines, SQL script, EMS definitions and file system deployment. Overall, this process became so complex that even a “simple” composite deployment could easily take 2-3 hours.

By splitting the composite into containers and building our composite structure on top of Docker Compose, deployment times were now down to minutes (up to 5 minutes for container pulls and restarts). This is a huge improvement over existing deployment times.

Containerizing a BusinessWorks Stack

Mon, 27 Feb 2023 14:08:54 +0000

Containerizing BusinessWorks 5 comes with its own set of challenges. Most of these are related to the surrounding ecosystem and the architectures that have evolved around it.

In a classic scenario, a BusinessWorks engine runs within an administrator domain and reports its lifecycle through Hawk. Deployment of an engine is also typically handled by a combination of these tools.

It is important to note that only BusinessWorks provides the interface implementations. The other tools are used to manage/monitor/maintain BW engines and keep them running.

Containerizing TIBCO BusinessWorks 5

Sun, 09 Aug 2020 10:08:54 +0000

Preparation

To prepare the container build, I downloaded the current versions of TRA/BW/EMS from the TIBCO edelivery platform.

I downloaded the following artifacts:

TIB_TRA_5.11.0_linux_x86_64.zip
TIB_BW_5.14.0_linux26gl23_x86_64.zip
TIB_rv_8.4.6_linux_x86.zip
TIB_ems_8.5.1_linux_x86_64.zip

Now to bring those together into a container I copied all of those into a tibco-businessworks-runtime directory.

Installation

To support a headless installation, the TIBCO universal installer uses silent files. I attached my silent file at the end of this post.

The Dockerfile is also attached.