Add warnings re docker build on windows (closes #324)
This commit is contained in:
parent
45591c122c
commit
1334596e30
10
README.md
10
README.md
@ -23,6 +23,16 @@ Unpack the `*.pgp` files from the dump under `contrib/docker-compose/devel/keydu
|
||||
You can change the configuration by editing `contrib/docker-compose/devel/etc/hockeypuck.conf` and running `docker-compose restart`.
|
||||
To stop, run `docker-compose down`.
|
||||
|
||||
## Building docker on Windows
|
||||
|
||||
BEWARE that if you are building a docker image on Windows, you MUST clone this repository with `autocrlf` disabled:
|
||||
|
||||
```
|
||||
git clone --config core.autocrlf=false https://github.com/hockeypuck/hockeypuck
|
||||
```
|
||||
|
||||
See https://stackoverflow.com/questions/53165471/building-docker-images-on-windows-entrypoint-script-no-such-file-or-directory
|
||||
|
||||
# Production deployment with docker-compose (RECOMMENDED for most users)
|
||||
|
||||
You can use `docker-compose` to build and deploy a standalone Hockeypuck instance in a production environment.
|
||||
|
@ -10,11 +10,21 @@ NB: all the below assume that you have `cd`-ed into this directory first.
|
||||
|
||||
# Supported platforms
|
||||
|
||||
Tested on Ubuntu 22.04 and Debian 11 (bullseye), with dependencies installed using `./setup.bash`.
|
||||
Tested on Ubuntu 22.04 and Debian 12 (bookworm), with dependencies installed using `./setup.bash`.
|
||||
|
||||
Other platforms may work but will require some customization.
|
||||
At minimum, docker (v18.06+) and docker-compose (v1.22+) must be installed in advance.
|
||||
|
||||
## Building docker on Windows
|
||||
|
||||
BEWARE that if you are building a docker image on Windows, you MUST clone this repository with `autocrlf` disabled:
|
||||
|
||||
```
|
||||
git clone --config core.autocrlf=false https://github.com/hockeypuck/hockeypuck
|
||||
```
|
||||
|
||||
See https://stackoverflow.com/questions/53165471/building-docker-images-on-windows-entrypoint-script-no-such-file-or-directory
|
||||
|
||||
# Migration of legacy nginx deployments (!BREAKING CHANGES!)
|
||||
|
||||
If you created a standalone deployment before April 2023, you will need to migrate from nginx to haproxy.
|
||||
|
Loading…
x
Reference in New Issue
Block a user