- 4,289
- 1,469
- NAS
- DS4l8play, DS202j, DS3623xs+, DSM 8.025847-𝘣𝘦𝘵𝘢
Most of the Docker images I use are from the "latest" category. If I wanted to test the "beta" image, or a specific release, a new container is created.
Being lazy, I don't want to re-enter my paths, environmental variables, etc.
What's the best way to do this? Poking around Synology's Docker GUI I'm guessing I could export the settings from the "latest" container, and then import those settings into the "beta" container. Would that work?
Or would I simply stop the "lastest" container... and rename it from "something" to "something-latest-save"... and then rename the "beta" container from "something-beta" to "something"? If I did that would the new "something" container inherit the settings from the original "something" container?
I hope I've made this clear. Basically I'd like to try out a beta (or develop) image, with the ability to revert to the lasted image... with the minimum of fuss and effort.
Being lazy, I don't want to re-enter my paths, environmental variables, etc.
What's the best way to do this? Poking around Synology's Docker GUI I'm guessing I could export the settings from the "latest" container, and then import those settings into the "beta" container. Would that work?
Or would I simply stop the "lastest" container... and rename it from "something" to "something-latest-save"... and then rename the "beta" container from "something-beta" to "something"? If I did that would the new "something" container inherit the settings from the original "something" container?
I hope I've made this clear. Basically I'd like to try out a beta (or develop) image, with the ability to revert to the lasted image... with the minimum of fuss and effort.