ComradeMiao@lemmy.world to Selfhosted@lemmy.worldEnglish · 2 年前Your favorite lesser known docker container?message-squaremessage-square76fedilinkarrow-up1147arrow-down16file-text
arrow-up1141arrow-down1message-squareYour favorite lesser known docker container?ComradeMiao@lemmy.world to Selfhosted@lemmy.worldEnglish · 2 年前message-square76fedilinkfile-text
minus-squareshaserlark@sh.itjust.workslinkfedilinkEnglisharrow-up1·2 年前So would this work well e.g. with the the *arr stack? Because most of the services wouldn’t even need to run always
minus-squareAustralianSimon@lemmy.worldlinkfedilinkEnglisharrow-up4·edit-22 年前How would the timed tasks be handled if they’re offline
minus-squareBrianTheeBiscuiteer@lemmy.worldlinkfedilinkEnglisharrow-up2·2 年前It probably would work well with those as long as the startup time was quick (my containers come up almost instantly) and the initiating clients can handle a bit of latency. I didn’t notice any hiccups in my use at all.
So would this work well e.g. with the the *arr stack? Because most of the services wouldn’t even need to run always
How would the timed tasks be handled if they’re offline
It probably would work well with those as long as the startup time was quick (my containers come up almost instantly) and the initiating clients can handle a bit of latency. I didn’t notice any hiccups in my use at all.