Manuel Hutter
Manuel Hutter
I'm a bit confused; which user starts the service?
A note about the workaround: What probably fixes the issue is `mode: '0644'`, not `owner: '{{ ansible_user }}'`. > Running ps aux | grep docker shows that the docker container...
Hmm, a possible workaround would be a task that runs conditionally, but implementing and then maintaining this is a PITA... Is this specific to certain Versions of Ansible?
What's the purpose behind this change? The point of `docker rm CONTAINERname` is to avoid conflicts when running `docker run`. To update the image before (re)starting, only `ExecStartPre=/usr/bin/docker pull user/image`...
Hi @silvio 👋 No, service templates are currently not supported and I don't plan on supporting them in the future, mostly because I'm not actively using this role anymore. From...
To be honest I don't remember exactly... I usually bootstrap my server with something like https://gist.github.com/mhutter/1682948 anyway...
We want to set fields like the default admin password, HTTP secrets and similar. In our pipeline we use `helm template` to render out all manifests, and then use ArgoCD...
This is a bug in `cargo-audit`, tracked in https://github.com/RustSec/rustsec/issues/300. It was fixed in v0.15 of cargo-audit.
What I usually do as a workaround in those cases: * use the `--immediate` flag * connect to the app directly (bypassing gin alltogether)
Should be possible by setting `AccessLog "/dev/stdout"` but needs testing