This guide explains how to create and deploy a Bun app. To run this example, follow these steps:

1. Install the CLI. Use the unikraft CLI or the legacy kraft CLI. You need a BuildKit builder. The easiest way to get one is via Docker. Alternatively, you can also directly set up and use BuildKit, see the quick start.

   Note: The unikraft CLI is the current standard, while kraft is the legacy version. Choose one of the CLIs below and only run the commands associated with it for the rest of this guide.

2. Clone the examples repository and cd into the examples/httpserver-bun directory:

   git clone https://github.com/unikraft-cloud/examples
   cd examples/httpserver-bun/

Make sure to log into Unikraft Cloud and pick a metro close to you. This guide uses fra (Frankfurt, 🇩🇪):

Using the unikraft CLI (Recommended)

unikraft login

or

Using the legacy kraft CLI

# Set Unikraft Cloud access token
export UKC_TOKEN=token
# Set metro to Frankfurt, DE
export UKC_METRO=fra

When done, invoke the following command to deploy this app on Unikraft Cloud:

Using the unikraft CLI (Recommended)

unikraft build . --output <my-org>/httpserver-bun:latest
unikraft run --metro fra \
  -m 512M \
  -p 443:3000/tls+http \
  --scale-to-zero policy=on,cooldown-time=1000 \
  --image <my-org>/httpserver-bun:latest

or

Using the legacy kraft CLI

kraft cloud deploy \
  -M 512Mi \
  -p 443:3000/tls+http \
  --scale-to-zero on \
  --scale-to-zero-cooldown 1s \
  .

The output shows the instance address and other details:

Using the unikraft CLI (Recommended)

metro:        fra
name:         httpserver-bun-700mp
uuid:         e467a880-075c-41e0-97ac-88e3e938523e
state:        starting
image:        <my-org>/httpserver-bun
resources:
  memory:     512MiB
  vcpus:      1
service:
  uuid:       00cddace-e5e1-be6e-3423-86cccb5a1031
  name:       quiet-pond-ao44imcg
  domains:
  - fqdn:     quiet-pond-ao44imcg.fra.unikraft.app
networks:
- uuid:       3e41aab5-96c3-23e8-4afc-e2109f3f60de
  private-ip: 10.0.3.3
  mac:        12:b0:6e:91:eb:5a
timestamps:
  created:    just now

or

Using the legacy kraft CLI

[●] Deployed successfully!
 │
 ├───────── name: httpserver-bun-700mp
 ├───────── uuid: e467a880-075c-41e0-97ac-88e3e938523e
 ├──────── metro: https://api.fra.unikraft.cloud/v1
 ├──────── state: starting
 ├─────── domain: https://quiet-pond-ao44imcg.fra.unikraft.app
 ├──────── image: oci://unikraft.io/<my-org>/httpserver-bun@sha256:dfcbee1efe0d8a1d43ab2dab70cf1cc5066bb1353aa1c528c745533d2cc33276
 ├─────── memory: 512 MiB
 ├────── service: quiet-pond-ao44imcg
 ├─ private fqdn: httpserver-bun-700mp.internal
 └─── private ip: 10.0.3.3

In this case, the instance name is httpserver-bun-700mp and the address is https://quiet-pond-ao44imcg.fra.unikraft.app. They're different for each run.

Use curl to query the Unikraft Cloud instance of the Bun HTTP web server:

curl https://quiet-pond-ao44imcg.fra.unikraft.app

Hello, World!

You can list information about the instance by running:

Using the unikraft CLI (Recommended)

unikraft instances list

METRO  NAME                  STATE    IMAGE                    ARGS  MEMORY  VCPUS  FQDN                                  CREATED
fra    httpserver-bun-700mp  running  <my-org>/httpserver-bun        512MiB  1      quiet-pond-ao44imcg.fra.unikraft.app  2 minutes ago

or

Using the legacy kraft CLI

kraft cloud instance list

NAME                  FQDN                                  STATE    STATUS       IMAGE                                                 MEMORY   VCPUS  ARGS  BOOT TIME
httpserver-bun-700mp  quiet-pond-ao44imcg.fra.unikraft.app  running  since 3mins  oci://unikraft.io/<my-org>/httpserver-bun@sha256:...  512 MiB  1            289.03 ms

When done, you can remove the instance:

Using the unikraft CLI (Recommended)

unikraft instances delete httpserver-bun-700mp

or

Using the legacy kraft CLI

kraft cloud instance remove httpserver-bun-700mp

To customize the app, update the files in the repository, listed below:

• Kraftfile: the Unikraft Cloud specification
• Dockerfile: the Docker-specified app filesystem
• server.ts: the Bun server implementation

Lines in the Kraftfile have the following roles:

• spec: v0.7: The current Kraftfile specification version is 0.7.

• runtime: base-compat:latest: The kernel to use.

• rootfs: Build the app root filesystem. source: ./Dockerfile means the filesystem is built using the Dockerfile. format: erofs means the filesystem type is EROFS.

• cmd: ["/usr/bin/bun", "run", "/usr/src/server.ts"]: Use /usr/bin/bun run /usr/src/server.ts as the starting command of the instance.

Lines in the Dockerfile have the following roles:

• FROM scratch: Build the filesystem from the scratch container image, to create a base image.

• COPY ...: Copy required files to the app filesystem: the bun binary executable, libraries, configuration files, the /usr/src/server.ts implementation.

• RUN ...: Run specific commands to generate or to prepare the filesystem contents.

The following options are available for customizing the app:

• If you only update the implementation in the server.ts source file, you don't need to make any other changes.

• If you want to add extra files, you need to copy them into the filesystem using the COPY command in the Dockerfile.

• If you want to replace server.ts with a different source file, update the cmd line in the Kraftfile and replace /usr/src/server.ts with the path to your new source file.

• More extensive changes may require extending the Dockerfile (see Dockerfile syntax reference).

Use the --help option for detailed information on using Unikraft Cloud:

Using the unikraft CLI (Recommended)

unikraft --help

or

Using the legacy kraft CLI

kraft cloud --help

Or visit the CLI Reference or the legacy CLI Reference.