![]() If you made an update, but the new version doesn't work or you just want to go back to the old one, just put an empty file called "recover" inside the "save"-folder and restart the container. If not, there will be a message inside the log. Update checkĮvery sunday the container will check if the installed version is still up-to-date. If you want to keep more than just your previous version, you have to do this by yourself. There will be no versioning inside the backup-script. The backup is located in the "backup"-folder within the "save"-folder. If you set the updater to 0, but you still want to update to a newer version, just put a empty file called "update" inside the "save"-folder and restart the container. Most likely try 0x10000 instead) Not needed for Box86 Specify the offset of qemu (Only use if you're facing an error with the default value. If set to 1, the updater will make an backup of the current server before updating to a newer version.Ĭontainer will enter debug mode ( -> no server will start, only the helper) If set to 1, an updater, which runs on every start of the container, checks & updates the server to the newest version if necessary. If set to 1, the system will apt update and upgrade on every restart If set to 1, the system will generate an ini-file inside the "save"-folder and will use this file at startup During that time your CPU load will be pretty high. With predownloaded tags you can update the server either by using the integrated updater OR you can pull the latest predownloaded image and redeploy your container.Next go to the 'logs' directory and 'cat' the content of the first log that ends with '_1.log'
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |