barkstack/pawsql
Public Access
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: run managed containers from PawSQL image
All checks were successful
Build and Push Image / docker-build-and-push (push) Successful in 5m3s
Details
Test and Release PawSQL / test (push) Successful in 44s
Details
Test and Release PawSQL / release (push) Successful in 8s
Details

Browse Source
This commit is contained in:
Shaun Campbell
2026-09-15 20:38:01 -04:00
parent c1f1362ea0
commit 4e305d67e3
2 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@@ -33,10 +33,11 @@ docker build -t pawsql .
docker run --rm --publish 5432:5432 \
--volume "$PWD/Barkfile:/etc/pawsql/Barkfile:ro" \
--volume "$PWD/tls:/etc/pawsql/tls:ro" \
--volume /var/run/docker.sock:/var/run/docker.sock \
pawsql
```
The provided image contains only PawSQL and is suitable for external `upstream` routes. Managed PostgreSQL routes require native PawSQL or a custom image that supplies a Docker CLI and access to the Docker Engine, typically through the Docker socket.
The supplied image includes the Docker CLI so managed `postgres` routes can create, start, and stop their containers through the mounted Docker socket. The socket grants PawSQL root-equivalent control of the Docker host; mount it only for trusted Barkfiles and trusted administrators.
## Barkfile