Description
Instead of simply exiting, the server binary should wait for a kill signal
Purpose / Use Case
When the server executable exits this also stops the container.
A stopped container cannot be updated which prevents bugfixes in the migration process to be applied.
You also can't just access the container console when it is stopped to follow the migration guide.
The easy solution is to not kill the server executable, but instead make it do nothing and wait for an exit signal. This prevents data corruption, allows container updates and gives access to the container console.
Additional Information (optional)
Its exactly the same as #266.
I am using bichon on truenas community edition. I don't consider myself a docker or container expert. There are a lot of other things I want to give priority so having an easy upgrade / migration mechanism is essential for me. However I am usually able to find solutions for problems, however its annoying and in this case, imo, unneccesarily complicated.
I do get that manual work is sometimes necessary and thats perfectly fine. At the same time I feel it should not be so complicated. At least, please give some instructions on how to access a stopped container in the wiki.
Finally I want to express my appreciation for this project. I do recognize and commend you for your work on bicon. I love it!
Description
Instead of simply exiting, the server binary should wait for a kill signal
Purpose / Use Case
When the server executable exits this also stops the container.
A stopped container cannot be updated which prevents bugfixes in the migration process to be applied.
You also can't just access the container console when it is stopped to follow the migration guide.
The easy solution is to not kill the server executable, but instead make it do nothing and wait for an exit signal. This prevents data corruption, allows container updates and gives access to the container console.
Additional Information (optional)
Its exactly the same as #266.
I am using bichon on truenas community edition. I don't consider myself a docker or container expert. There are a lot of other things I want to give priority so having an easy upgrade / migration mechanism is essential for me. However I am usually able to find solutions for problems, however its annoying and in this case, imo, unneccesarily complicated.
I do get that manual work is sometimes necessary and thats perfectly fine. At the same time I feel it should not be so complicated. At least, please give some instructions on how to access a stopped container in the wiki.
Finally I want to express my appreciation for this project. I do recognize and commend you for your work on bicon. I love it!