Appearance

Studio Recipes: Native Integration ​

Use these recipes to combine containerized assets with native Windows applications without breaking isolation.

What You'll Learn

  • How to open container files with native Adobe Reader
  • How to run native browsers alongside containerized instances
  • How to pick isolation modes and layers for mixed native-container workflows

Native Integration Recipes ​

Open Container Files with Native Adobe Reader ​

Run a containerized file set with a native Adobe Reader install while keeping writes inside the sandbox. The adobe/disable-reader-sandbox layer maintains compatibility with Reader.

bash
turbo run mypdfs,adobe/disable-reader-sandbox --isolate=write-copy --startup-file="C:\\Program Files (x86)\\Adobe\\Acrobat Reader DC\\Reader\\AcroRd32.exe" -- C:\\MyPDFs\\test.pdf

Validate:

  • Confirm Adobe Reader opens the file from C:\MyPDFs without prompting for native writes.
  • Modify the PDF or annotations and verify the changes stay in the container sandbox.
  • Restart the container to ensure the Reader sandbox layer remains applied.

Run Native Edge or Chrome Alongside Container Instances ​

Use isolation to avoid conflicts from native browser lockfiles when you run the same browser inside a container. Choose a prebuilt isolation layer when you want to avoid manual flag management.

bash
turbo run edge --isolate=write-copy
turbo run turbobuild/isolate-edge-wc,edge

Validate:

  • Launch a native Edge or Chrome session, then start the container command and confirm both run simultaneously.
  • Check that the container session starts without lockfile errors.
  • If you use the isolation layer, verify it appears in turbo images and applies without additional flags.

Turbo.net © 2025