hostsharing/hs.hsadmin.ng
6
0
Fork 0
Code Pull Requests 3 Activity

add aliases podman-start und podman-use

Browse Source
This commit is contained in:
Michael Hoennig 2022-09-15 11:19:04 +02:00
parent 01d9cbd711
commit 430f75ea15
2 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.aliases
View File

@ -12,6 +12,8 @@ gradleWrapper () {
rm $TEMPFILE rm $TEMPFILE
} }
alias podman-start='systemctl --user enable --now podman.socket && systemctl --user status podman.socket && ls -la /run/user/$UID/podman/podman.sock'
alias podman-use='export DOCKER_HOST="unix:///run/user/$UID/podman/podman.sock"; export TESTCONTAINERS_RYUK_DISABLED=true'
alias gw=gradleWrapper alias gw=gradleWrapper
alias pg-sql-run='docker run --name hsadmin-ng-postgres -e POSTGRES_PASSWORD=password -p 5432:5432 -d postgres:13.7-bullseye' alias pg-sql-run='docker run --name hsadmin-ng-postgres -e POSTGRES_PASSWORD=password -p 5432:5432 -d postgres:13.7-bullseye'

8
README.md
View File

@ -524,9 +524,15 @@ Summary for Debian-based Linux systems:
sudo apt-get -y install podman sudo apt-get -y install podman
``` ```
2Then start it like this:
```shell
systemctl --user enable --now podman.socket systemctl --user enable --now podman.socket
systemctl --user status podman.socket systemctl --user status podman.socket
ls -la /run/user/$UID/podman/podman.sock ls -la /run/user/$UID/podman/podman.sock
```
These commands are also available in `.aliases` as `podman-start`.
#### Use the Command Line to Run the Tests Against the Podman Daemon #### Use the Command Line to Run the Tests Against the Podman Daemon
@ -538,6 +544,8 @@ export DOCKER_HOST="unix:///run/user/$UID/podman/podman.sock"
export TESTCONTAINERS_RYUK_DISABLED=true export TESTCONTAINERS_RYUK_DISABLED=true
``` ```
These commands are also available in `.aliases` as `podman-use`.
Disabling RYUK is necessary, because it's not supported by Podman. Disabling RYUK is necessary, because it's not supported by Podman.
Supposedly this means that containers are not properly cleaned up after test runs, Supposedly this means that containers are not properly cleaned up after test runs,
but I could not see any remaining containers after test runs. but I could not see any remaining containers after test runs.