Closed TheBlueKingLP closed 1 year ago
Short question as I can't reproduce it when I start/restart the container after my compose/stack is deployed:
Do you stop the compose/stack and start it again (which is basically: stops and trashes the container, recreates it, start it) or just a restart of the docker container when the comose/stack is already up?
If it's the 1st I can confirm this - a new container is created this way and the old one with mono already installed is trashed. Then it's downloading mono once. It's persistent start/stop/restart of the container. Unless I stop the whole compose/stack it does not download it again upon restart.
Can you confirm this behavior?
@TheBlueKingLP can you answer kero's question above? (Provided you have the time for it.)
In the meantime I'm closing this, since I also think it is because of the compose stack being recreated, which means it is by design. Feel free to reopen this if the behaviour is not because of compose
## PLEASE READ BEFORE POSTING YOUR ISSUE
Please create GitHub issues only for bugs and feature requests. If you need help with using Shoko or have a question, join us on Discord.
https://discord.gg/vpeHDsg
===== Guidelines ====
VERSION INFORMATION
Server Version: 4.1.2.0
Desktop Version: Not Applicable
If you've compiled your own version, please use the last commit you compiled.
LOG FILE
DESCRIPTION
Packages related to MONO is being downloaded every time the container is started. The problem is that
libc-bin
will take many minutes to download. 7 minutes for me to be exact.STEPS TO REPRODUCE
AVDUMP_MONO=true
.