-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More In-depth Readme #13
Comments
https://www.baeldung.com/ops/docker-copying-files#copy-to-docker-container This website has some tips for interacting with a docker container. Not sure if it's quite possible with ours, but worth a try until anything else happens. |
#9 Might be related as well |
Hi! Sorry, my work on this image has ground to a halt a little over the last year. As best as I remember, the nature of the way the folder structures that the modding frameworks use is a little complex and I was last thinking of how best to incorporate this into the container in an elegant way. You can see this reflected in the other issues on this repo. I'll get back to work on this - watch this space... |
No worries! Thanks for your prompt responses. I look forward to future updates :) EDIT: I feel like the easiest way to fix this would be to just allow someone to bind the /ror2/ working directory to a local folder, but with the setup building the container being heavily automated with +49 or so steps it walks through, having more robust documentation on what this automated process is doing and how users can change variables would help a ton! |
Hi, we've been using this image a little after the huge new update. I've expanded the README with a dedicated "Modding" section: https://github.com/FragSoc/riskofrain2-docker#modding. @Binary-2 let me know what you think! |
That's perfect! I look forward to testing this in a new container! |
Hopefully closed in 3f0dd03, feel free to reopen if there's anything you want to add :) |
I've read through most of the documentation for this docker image and have set up a server as I'd like, but most of the mod settings are baked into the container.
While this is nice for simplicity's sake, this docker completely removes a lot of the customization you have with config files generated by plugins themselves along with other configuration files now unreachable.
This container runs great, but would it be possible to expose more of the files through volumes/binds and environment variables or would this ruin the efficiency of the container?
EDIT: I can't even find out where it's installed the container files as everything in /var/lib/docker/containers/{container_id}/ is just related to runtime variables and not the gamefiles or steam CMD
The text was updated successfully, but these errors were encountered: