Skip to content

Commit 16fa986

Browse files
committed
add keycloak images link
1 parent 80b51d8 commit 16fa986

File tree

1 file changed

+15
-1
lines changed

1 file changed

+15
-1
lines changed

docs/docs/how-tos/nebari-local.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,7 @@ sudo echo "172.18.1.100 <domain>" | sudo tee -a /etc/hosts
128128

129129
### Exposing container network (for MacOS)
130130

131-
Docker for macOS does not expose container networks directly on the macOS host, for this we will use
131+
Docker for macOS does not expose container networks directly on the MacOS host, for this we will use
132132
[docker-mac-net-connect](https://github.com/chipmk/docker-mac-net-connect), which lets you connect directly
133133
to Docker-for-Mac containers via IP address. You can install and start it with following command:
134134

@@ -145,6 +145,20 @@ $ sudo brew services start chipmk/tap/docker-mac-net-connect
145145
You can skip this section if you have an x86_64 machine. If you're using Mac M1, then the x86_64 docker images
146146
will not work out of the box. You would need to use images that are built with support for arm as well.
147147

148+
We're building all the docker images for both platforms except external images. The only external image relevant
149+
here is keycloak. You'd need to update the keycloak image for the deployment, which can be done by adding the
150+
override for the keycloak deployment to update the image:
151+
152+
```yaml
153+
security:
154+
keycloak:
155+
initial_root_password: <SANITIZED>
156+
overrides:
157+
image:
158+
repository: quay.io/nebari/keycloak
159+
tag: sha-b4a2d1e
160+
```
161+
148162
## Deploying Nebari
149163
150164
With the `nebari-config.yaml` configuration file now created, Nebari can be deployed for the first time with:

0 commit comments

Comments
 (0)