File tree Expand file tree Collapse file tree 1 file changed +15
-1
lines changed Expand file tree Collapse file tree 1 file changed +15
-1
lines changed Original file line number Diff line number Diff line change @@ -128,7 +128,7 @@ sudo echo "172.18.1.100 <domain>" | sudo tee -a /etc/hosts
128
128
129
129
### Exposing container network (for MacOS)
130
130
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
132
132
[ docker-mac-net-connect] ( https://github.com/chipmk/docker-mac-net-connect ) , which lets you connect directly
133
133
to Docker-for-Mac containers via IP address. You can install and start it with following command:
134
134
@@ -145,6 +145,20 @@ $ sudo brew services start chipmk/tap/docker-mac-net-connect
145
145
You can skip this section if you have an x86_64 machine. If you're using Mac M1, then the x86_64 docker images
146
146
will not work out of the box. You would need to use images that are built with support for arm as well.
147
147
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
+
148
162
## Deploying Nebari
149
163
150
164
With the ` nebari-config.yaml` configuration file now created, Nebari can be deployed for the first time with:
You can’t perform that action at this time.
0 commit comments