Skip to content

Commit

Permalink
guides: Updated Nginx version And network syntax
Browse files Browse the repository at this point in the history
Signed-off-by: Ansuman Sahoo <[email protected]>
  • Loading branch information
unsuman committed Mar 2, 2024
1 parent 8c99b9f commit 54ca8d7
Showing 1 changed file with 12 additions and 6 deletions.
18 changes: 12 additions & 6 deletions content/guides/using-the-app-catalog.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ As a user it shouldn't matter to you.
You can list the applications in the registry by using:

```bash
$ kraft pkg ls --apps --all --update
kraft pkg ls --apps --all --update
```

Check failure on line 21 in content/guides/using-the-app-catalog.mdx

View workflow job for this annotation

GitHub Actions / Markdown Linter

Fenced code blocks should be surrounded by blank lines [Context: "```"]
```

Check failure on line 22 in content/guides/using-the-app-catalog.mdx

View workflow job for this annotation

GitHub Actions / Markdown Linter

Fenced code blocks should be surrounded by blank lines [Context: "```"]

Check failure on line 22 in content/guides/using-the-app-catalog.mdx

View workflow job for this annotation

GitHub Actions / Markdown Linter

Fenced code blocks should have a language specified [Context: "```"]
TYPE NAME VERSION FORMAT MANIFEST INDEX PLAT
Expand Down Expand Up @@ -82,7 +82,7 @@ If you are running natively (for maximum performance), and if you likely have ha
Similarly, we can pull and run Nginx:

```bash
kraft run -W unikraft.org/nginx
kraft run -W unikraft.org/nginx:1.15
```

Check failure on line 86 in content/guides/using-the-app-catalog.mdx

View workflow job for this annotation

GitHub Actions / Markdown Linter

Fenced code blocks should be surrounded by blank lines [Context: "```"]
```

Check failure on line 87 in content/guides/using-the-app-catalog.mdx

View workflow job for this annotation

GitHub Actions / Markdown Linter

Fenced code blocks should be surrounded by blank lines [Context: "```"]

Check failure on line 87 in content/guides/using-the-app-catalog.mdx

View workflow job for this annotation

GitHub Actions / Markdown Linter

Fenced code blocks should have a language specified [Context: "```"]
i using arch=x86_64 plat=qemu
Expand All @@ -99,7 +99,7 @@ Note that the Nginx server starts but waits for a connection.
In order to connect to it, we need to pass a port mapping, similar to [`docker` commands](https://docs.docker.com/network/#published-ports):

```bash
kraft run -W -p 8080:80 unikraft.org/nginx
kraft run -W -p 8080:80 unikraft.org/nginx:1.15
```

Check failure on line 103 in content/guides/using-the-app-catalog.mdx

View workflow job for this annotation

GitHub Actions / Markdown Linter

Fenced code blocks should be surrounded by blank lines [Context: "```"]
```

Check failure on line 104 in content/guides/using-the-app-catalog.mdx

View workflow job for this annotation

GitHub Actions / Markdown Linter

Fenced code blocks should be surrounded by blank lines [Context: "```"]

Check failure on line 104 in content/guides/using-the-app-catalog.mdx

View workflow job for this annotation

GitHub Actions / Markdown Linter

Fenced code blocks should have a language specified [Context: "```"]
i using arch=x86_64 plat=qemu
Expand All @@ -113,6 +113,12 @@ oOo oOO| | | | | (| | | (_) | _) :_
Telesto 0.16.1~b1fa7c5
```


<Info>
You can use nginx version 1.25 instead of version 1.15 by appending `:1.25` to the `kraft run` command.
For example: `kraft run -W unikraft.org/nginx:1.25`
</Info>

With the command above we mapped the local port `8080` to the internal Nginx Unikraft port `80`:
Query the server to get the index page:

Expand Down Expand Up @@ -140,7 +146,7 @@ For an IP-based network connection, you can use a bridged interface.
First create a bridge interface, as `root` (prefix with `sudo` if required):

```bash
sudo kraft run --network bridge:virbr0 unikraft.org/nginx
sudo kraft run --network virbr0 unikraft.org/nginx:1.15
```
```
i using arch=x86_64 plat=qemu
Expand Down Expand Up @@ -247,7 +253,7 @@ If, instead of port mapping, you want to use bridge networking, follow the steps
1. Run as `root` (prefix with `sudo` if required):

```bash
kraft run --network bridge:virbr0 .
kraft run --network virbr0 .
```

1. Query the unikernel instance:
Expand Down Expand Up @@ -304,7 +310,7 @@ If, instead of port mapping, you want to use bridge networking, follow the steps
1. Run as `root` (prefix with `sudo` if required):

```bash
sudo KRAFTKIT_BUILDKIT_HOST=docker-container://buildkitd kraft run --network bridge:virbr0 .
sudo KRAFTKIT_BUILDKIT_HOST=docker-container://buildkitd kraft run --network virbr0 .
```

1. Query the unikernel instance:
Expand Down

0 comments on commit 54ca8d7

Please sign in to comment.