I am hoping someone here can help me with this issue.
I am using the official 3.4.10 community edition rundeck image.
I have noticed that some information does not persist across docker restarts without putting it on some form of a volume (host or named). Items I have found thus far are
#paths listed in this part are in the container
/home/rundeck/libext (plugin directory)
/home/rundeck/etc (ACL location)
job execution logs (not entirely sure where those live)
I prefer to use host volumes over named volumes when possible. I worry a co-worker might accidentally “docker-compose down -v” and *poof* my named volumes would be gone!
When I set up a host volume for the /home/rundeck/etc folder using the following
The volume is created properly, but not all the files that are supposed to show up in the /home/rundeck/etc folder do.
We should see
admin.aclpolicy framework.properties preferences.properties profile profile.bat project.properties
But instead, we only see the “framework.properties” file.
I ensured that the folders have the correct permissions before bringing up my docker-compose stack by running a chown -R 1000:root /local/etc/path
If I use a named volume instead (like this)
The data in /home/rundeck/etc persistes thru restarting my docker-compose stack, but is vulnerable to a purge or a docker-compose down -v, which makes me less than comfortable.
So, after all that I guess I have two questions
In addition to my first answer (based on a standard config, so, you can ignore it ;-), I saw the same behavior using persistent volumes on
/home/rundeck/etc and you’re facing this. Could you add your use case on that thread?
Putting all the files on the local directory like a “global template” fixes that (as a “dirty” workaround) but certainly, the container must generate the files automatically.
Your reply is much appreciated 😊
I ended up using a specific file volume, like this –
And will add additional ACLS in the same manner as needed.
I also updated the git issue you linked to add my voice 😊
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/db267ce2-47e6-43cf-adef-80b53fd68ef4n%40googlegroups.com.