Skip to content

Commit caaee0f

Browse files
committed
bugfix-docker > staging: documented the issue
1 parent 6d15464 commit caaee0f

File tree

2 files changed

+36
-0
lines changed

2 files changed

+36
-0
lines changed

Diff for: .gitignore

+1
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@
88
# ----------------------------------------------------------------
99

1010
!/README.md
11+
!/ISSUES.md
1112
!/LICENCE
1213
!/justfile
1314
!/Cargo.toml

Diff for: ISSUES.md

+35
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
# Issues #
2+
3+
## Posix bug ##
4+
5+
### Description ###
6+
7+
When expanding the environment variable `WD`
8+
from [docker-compose.yaml](docker-compose.yaml) in [Dockerfile](Dockerfile),
9+
and running `docker compose up --build -d ...`
10+
(see [justfile](justfile) > command: `just docker-build`)
11+
paths like `/usr/home/myapp` would be bafflingly
12+
replaced by `C:/Program Files/Git/usr/home/myapp`.
13+
14+
### Diagnosis ###
15+
16+
This bug occurs on Windows when using the Git Bash console
17+
as is a known issue, see <https://github.com/git-for-windows/build-extra/blob/main/ReleaseNotes.md>.
18+
19+
### Solution ###
20+
21+
Whilst there a new release of Git Bash may solve this issue,
22+
a work around that work with older versions is to simply replace
23+
24+
```.env
25+
DOCKER_WORKDIR="/usr/home/${DOCKER_APP}"
26+
```
27+
28+
via
29+
30+
```.env
31+
DOCKER_WORKDIR="//usr/home/${DOCKER_APP}"
32+
```
33+
34+
in the [.env](templates/template.env) file.
35+
By replacing `//` by `/`, such forced expansions are avoided.

0 commit comments

Comments
 (0)