You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: qemu_artifact.md
+37-20Lines changed: 37 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,38 +10,56 @@ Given the size of the image, the first VM using it on a node might take a while
10
10
11
11
## Creating a bare-metal instance
12
12
13
-
We launch an Ubuntu 22 bare-metal instance; we're using the `c6g.metal` instance type in this case, but any ARM instance type is sufficient for our purposes.
13
+
We launch an Ubuntu 22 bare-metal instance; we're using the `c6g.metal` instance type in this case, but any ARM instance type is sufficient for our purposes. In the example below the region used is: `ap-south-1`.
git checkout da/qemu-rebasing # choose appropriate branch here
61
+
make init container-disk-image
62
+
```
45
63
46
64
### Build process
47
65
@@ -67,8 +85,7 @@ b. packer build (`qemu-arm64-nix.pkr.hcl`)
67
85
68
86
## Publish image for later use
69
87
70
-
Publish the built image to a registry of your choosing, and use the published image with KubeVirt.
71
-
88
+
Following `make init container-disk-image`, the generated image should be found in: `/path/to/postgres/output-cloudimg`. For portability the image is also bundled up as a docker image with the name: `supabase-postgres-test` . Publish the built docker image to a registry of your choosing, and use the published image with KubeVirt.
0 commit comments