femtek@lemmy.blahaj.zone to Selfhosted@lemmy.worldEnglish · 6 days agoPortainer 3.0 is coming, and here's what it means for you — Portainerportainer.ioexternal-linkmessage-square47linkfedilinkarrow-up10arrow-down10file-text
arrow-up10arrow-down1external-linkPortainer 3.0 is coming, and here's what it means for you — Portainerportainer.iofemtek@lemmy.blahaj.zone to Selfhosted@lemmy.worldEnglish · 6 days agomessage-square47linkfedilinkfile-text
minus-squaresurewhynotlem@lemmy.worldlinkfedilinkEnglisharrow-up0·5 days agoDo you know if there’s a way to pin to a version but have dockhand tell me if there is a new latest version tagged? Not having a clean rollback method is driving me nuts.
minus-squareShutUpWesley@piefed.ziplinkfedilinkEnglisharrow-up0·5 days agoYeah, version tags work fine. All my containers come from compose, and it follows whatever tags I declared there.
minus-squaresurewhynotlem@lemmy.worldlinkfedilinkEnglisharrow-up0·5 days agoThat’s my problem I mean. I want to use the tag (e.g. v8) but then be notified when v9 is out. And v8.1. I know the 8.1 would work.
Do you know if there’s a way to pin to a version but have dockhand tell me if there is a new latest version tagged? Not having a clean rollback method is driving me nuts.
Yeah, version tags work fine. All my containers come from compose, and it follows whatever tags I declared there.
That’s my problem I mean. I want to use the tag (e.g. v8) but then be notified when v9 is out. And v8.1. I know the 8.1 would work.