Repository navigation
Expand file tree
/
Copy pathdocker-compose.yml
More file actions
56 lines (53 loc) · 1.76 KB
/
Copy pathdocker-compose.yml
File metadata and controls
56 lines (53 loc) · 1.76 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
services:
vault:
image: hashicorp/vault:1.15.6
container_name: vault
ports:
- "8200:8200"
restart: unless-stopped
volumes:
- ./volumes/vault/logs:/vault/logs
- ./volumes/vault/file:/vault/file
- ./volumes/vault/plugins:/vault/plugins
environment:
# `plugin_directory` holds the custom algorand-pq secrets engine, built
# by scripts/build_vault_plugin.sh into the bind mount above.
VAULT_LOCAL_CONFIG: '{"storage": {"file": {"path": "/vault/file"}},"listener": {"tcp": {"address": "0.0.0.0:8200","tls_disable": true}},"api_addr": "http://vault:8200","ui": true,"plugin_directory": "/vault/plugins"}'
VAULT_ADDR: http://127.0.0.1:8200
cap_add:
- IPC_LOCK
# Vault spawns plugins with mlock enabled, and the plugin binary has no
# cap_ipc_lock of its own (setcap does not survive the bind mount), so it
# is bounded by RLIMIT_MEMLOCK. Docker Desktop defaults that to unlimited;
# dockerd on Linux (GitHub runners) defaults to 8 MiB, which the ~15 MB
# static plugin exceeds. It then dies with "cannot allocate memory" before
# the go-plugin handshake and Vault only reports the misleading "not
# compiled for this architecture" error.
ulimits:
memlock: -1
command: server
pawn:
build:
context: .
dockerfile: ./Dockerfile
image: pawn-dev
working_dir: /opt/app
command: sh -c 'yarn && yarn start:dev;'
container_name: pawn
env_file:
- .env
environment:
NODE_HOST: algod
NODE_PORT: "8080"
volumes:
- .:/opt/app/
- /opt/app/node_modules
ports:
- "3000:3000"
networks:
- default
- algokit_sandbox
networks:
algokit_sandbox:
external: true
name: algokit_sandbox_default