Last active
July 29, 2024 20:34
-
-
Save jpadams/789b259cb0cf7d2a166dc4f2fa588cc5 to your computer and use it in GitHub Desktop.
Thanks to @busla for sharing the original script, which I've modified a bit to use our registry alias
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
set -eoux pipefail | |
default_state_dir=/var/lib/dagger | |
engine_version=${1:-v0.6.0} | |
dagger_cache="dagger-cache" | |
dagger_runner="dagger" | |
podman volume create $dagger_cache || true | |
podman rm -f $dagger_runner || true | |
podman run \ | |
--name $dagger_runner \ | |
--restart always \ | |
-d \ | |
-v "$dagger_cache:$default_state_dir" \ | |
--privileged \ | |
registry.dagger.io/engine:"$engine_version" --debug |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@jpadams I got here from your comments about using dagger with podman on discord, and wanted to ask if you knew whether the latest dagger release v0.12.3 requires more than just symlinking docker-->podman client binary, which is all the documentation says is required to run with podman.
See here for more details on the problem I'm having running dagger in an environment with podman, but not docker.