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
Add `:<version>` to the end of the command to override the version.
158
+
159
+
```shell
160
+
dockerized node:15
161
+
```
162
+
163
+
164
+
**Listing versions**
165
+
166
+
To see which versions are available, run:
167
+
168
+
```shell
169
+
dockerized node:?
170
+
# or
171
+
dockerized node:
172
+
```
173
+
174
+
**Environment Variables**
175
+
155
176
Each command has a `<COMMAND>_VERSION` environment variable which you can override.
156
177
157
178
- `python`: `PYTHON_VERSION`
@@ -188,13 +209,6 @@ This allows you to "lock" your tools to specific versions for your project.
188
209
- Create a `dockerized.env` file in your project directory.
189
210
- All commands executed within this directory will use the settings specified in this file.
190
211
191
-
**Ad-hoc**
192
-
193
-
Add `:<version>` to the end of the command to override the version.
194
-
195
-
```shell
196
-
dockerized node:15
197
-
```
198
212
199
213
**Ad-hoc (Unix)**
200
214
@@ -213,12 +227,6 @@ dockerized node:15
213
227
dockerized node
214
228
```
215
229
216
-
**Ad-hoc (Windows Powershell)**
217
-
218
-
It's currently not known how to specify the version of a command in a Powershell script through environment variables.
219
-
220
-
As an alternative, you can create a `dockerized.env` file in the current directory.
221
-
222
230
## Localhost
223
231
224
232
Dockerized applications run within an isolated network. To access services running on your machine, you need to use `host.docker.internal` instead of `localhost`.
0 commit comments