-
Notifications
You must be signed in to change notification settings - Fork 60
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
Cannot use my own build dockerfile #22
Comments
Nope, mate. Everything you see is inhere. connect to it with
you can just read what is in the gitpush & dockerpush commands. They're just bashscripts. Also, the vrising server, let it build for a while. the logs outputs tons of errors anyway! It can take a decent amount of time (15 mins) on a slower system. |
Thanks for your reply. I did what you said, and waited, while ignoring the errors thrown, and after a while the server did start up, and I was able to connect. I guess my little NUC (J3160 with 4gb ram), is just on the low end side for running the server. |
Once it runs, it should be fine, depending on how much of that ram is available. |
First of all, thank you for sharing this! I am able to run the docker-compose file just fine out of the box (after adjusing the location of my server config files etc.).
Now, I wanted to make my own docker image using the provided Dockerfile. The build finishes fine, however, when I run the docker-compose with the new (local) image, wine somehow seems to crash, and the server hangs. Is there some build arguments I need to apply, which are not described in the readme file?
Sincerely, John
The text was updated successfully, but these errors were encountered: