Configure builder by default

[ptrus]

Fixes: #652

This PR configures the ROFL builder container image by default for new and upgraded ROFL apps. Also provides clearer error messages when the container runtime is missing or native builds aren't supported.

Everyone should now just run oasis rofl build (regardless of platform).

Note: This changes the built artifacts again, but builds should now be fully reproducible across environments when using the Docker builder.

Changes:

• Builder container image is now configured by default for new and upgraded apps
• Stream tar directly to sqfstar instead of extracting to disk
• Split builder images: minimal rofl-container-builder for container apps, full rofl-dev for raw Rust apps

Tested this (and got reproducable builts on):

• ubuntu with oasis rofl build --no-container (no builder)
• ubuntu with oasis rofl build (uses builder)
• macos with builder oasis rofl build (uses builder)

TODO:

• Consider adding a CLI version field to the manifest (set on init/upgrade) to track which CLI version created/modified it.
• update quickstart docs to not recommend docker run --platform linux/amd64 --volume .:/src -it ghcr.io/oasisprotocol/rofl-dev:main oasis rofl build anymore, once this is released
  • done in docs/rofl: Simplify rofl build instructions oasis-sdk#2411

[netlify]

✅ Deploy Preview for oasisprotocol-cli canceled.

Name	Link
🔨 Latest commit	3cbaa26
🔍 Latest deploy log	https://app.netlify.com/projects/oasisprotocol-cli/deploys/69380d8d8a51e90008324608

[kostko]

since rofl-dev image will now be more widely used, we might want to see if there's an easy way to reduce the size of it a bit

We could split it into two images, one that has the essential build tools for container-based apps (should be small) and the other that has Rust toolchain and more stuff. Then use the appropriate one when initializing/upgrading, depending on app kind (raw vs. container).

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Pull request overview

Copilot reviewed 16 out of 16 changed files in this pull request and generated 4 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 16 out of 16 changed files in this pull request and generated 3 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[kostko]

Nice work!

[kostko]

Was this also a problem before?

[ptrus]

It wasn't, but it's not 100% clear to me why. Maybe this is just a problem on macos, before we always used a docker container for building on macos. Will test out if this is macos specific.

[ptrus]

I figured out what the issue was. It wasn't related to the environment. The problem was that the padding was done on the host via f.Truncate (not in the builder container), and over the bind mount the container saw only the pre‑pad size. Doing either veritysetup verify or resizing the image fixed the issue (probably just due to touching it?). So I moved the padding to be run in the builder env and it fixes the issue. I have kept the veritysetup verify step, since it's useful as a sanity check, but have removed the resize since it's not needed.

[Copilot]

Pull request overview

Copilot reviewed 16 out of 16 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.