Open Hupfer29 opened 1 year ago
Hi andre, sorry to hear that, and also sorry for my late reply - my gihub emails were routed to archive automatically due to a bad rule in my mailbox... Hopefully you found a fix, if not, please let me know and add some more information. (do you use a composer file, or just run the image? What is your starting command?...) I personally don't know anything about Synology NAS, so i need more information.
Best regards Devidian
Hello Devidian,Thank you for your reply. I fixed it in the meantime. I used portainer to look inside the Container. This helped me to fix the configuration error I made. Everything was finw with the container itself. Ist there alread a 1.18 Version available?Kind regards,Andre--Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 05.04.23, 07:41 schrieb Maik Laschober @.***>:
Hi andre, sorry to hear that, and also sorry for my late reply - my gihub emails were routed to archive automatically due to a bad rule in my mailbox... Hopefully you found a fix, if not, please let me know and add some more information. (do you use a composer file, or just run the image? What is your starting command?...) I personally don't know anything about Synology NAS, so i need more information. Best regards Devidian —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
Great to hear!
There is always an image tagged with "unstable" containing the latest rc version (as 1.18 is not yet fully released) see https://hub.docker.com/r/devidian/vintagestory/tags
I always try to update the unstable branch as soon as i read the update news.
@Hupfer29 Can you provide details on what your configuration error and your solution was? I seem to having the same problem, that there are no world savedata. My "gamedata" folder in the docker and on the host are booth empty.
Hello Devidian,
at the end it was important to understand, how the path values in
the Docker configuration dialogue
the vintagestory serverconfig.json file
and the location of the world in the docker path are related to each other
To find it out and to understand this I needed “Portainer” to look into the container on the Synology NAS and the VintageStory installation on my PC to understand where the files are usually located.
Kind regards,
Andre
Von: Nid01 @.*** Gesendet: Dienstag, 30. Mai 2023 02:34 An: Devidian/docker-vintagestory Cc: Hupfer29; Mention Betreff: Re: [Devidian/docker-vintagestory] Does not react to changes in the seversettings (Issue #2)
@Hupfer29 https://github.com/Hupfer29 Can you provide details on what your configuration error and your solution was? I seem to having the same problem, that there are no world savedata. My "gamedata" folder in the docker and on the host are booth empty.
— Reply to this email directly, view it on GitHub https://github.com/Devidian/docker-vintagestory/issues/2#issuecomment-1567622516 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AVOLKT3QFU7IWKZAIP2BAZ3XIU55XANCNFSM6AAAAAAS3REHYY . You are receiving this because you were mentioned. https://github.com/notifications/beacon/AVOLKT2OMDLJSZAHFHZ7QR3XIU55XA5CNFSM6AAAAAAS3REHY2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS5OACXI.gif Message ID: @.***>
Hello devidian,
I'm using the docker container on a Synology NAS with DSM6.x. The container runs fine but it does not react to any changes of the serverconfog file. There is also not world saved in the docker folder.
I have also two minecraft servers running in docker. Both are saving worlds into the docker path of the NAS.
I'm starting the container from the GUI. A start from the shell (terminal) was not successful. I could not connect to the server.
Thank you, Andre