How updating to 'latest' version of 'latest' container image

[vincent1890]

Hello

I have a container with teamspeak:lasted but use image docker this does not update.
How to force the update without removing the current container?

Thank

[spikemixture]

I have been asking the same question for a long time.
I too want to update a container in docker without having to reinstall the image and setup again.

Appears qnap people don't use - or know how to update containers...

good luck.

[bilak]

I don't understand the qnap. I'm also aking for new docker version while this one is 2 years old. They even don't provide custom scripts to update the docker.
If anybody knows hot to update it manually please share the scripts.

Thanks

[vincent1890]

Yes I really don’t understand QNAP either especially that apparently a lot of people install https://www.portainer.io/ or other system to overcome this really recurring problem on internet in different forum and website
example:
https://blog.feutl.com/use-portainer-on-qnap
https://www.youtube.com/watch?v=pzWXOguQ3Lw

On this site some super explanation but unfortunately no information about the automation of container creation directly in Containerstation thanks to the file yml (yaml) Docker Compose unfortunately.
https://blog.linuxserver.io/2017/09/17/ ... s-on-qnap/

For example I wanted to use this alternative at least to overcome the problem without being obliged to install portainer but impossible because an error occurs open subject HERE:
viewtopic.php?f=354&t=155736

[vincent1890]

happy and unhappy to see that QNAP has done nothing since all this time about the problems raised by the community

[drewy]

A container is created from an image. The container is not supposed to exist forever, it’s a transient object.
You can’t upgrade the container, you grab a new image and create a new container from that image.
If you need to persist data between old and new containers then you need to store that data outside of the container.

Unless I misunderstand your ask, and I apologise if I did, what your asking for is not a fault of qnaps or dockers.....it’s just the way containers are designed to work.

[vincent1890]

A container is created from an image. The container is not supposed to exist forever, it’s a transient object.
You can’t upgrade the container, you grab a new image and create a new container from that image.
If you need to persist data between old and new containers then you need to store that data outside of the container.

Unless I misunderstand your ask, and I apologise if I did, what your asking for is not a fault of qnaps or dockers.....it’s just the way containers are designed to work.

Hello drewy

I am all agreed with your point of view but in this case why Qnap does not create a button on graphical interface to delete and recreate a container with the same config as the previous have no more than that because being obliged to recreate by hand each container each time with ip, name, network, montages, resource limits, etc this is a real delight on the QNAP Containerstation

If at a minimum Qnap provided the elements and explanation to allow an example automation here viewtopic.php?f=354&t=155736&p=757754 it would be fine but it is not unfortunately.

[drewy]

Not as simple as you’d like it but you can do similar if you click on the create application button and then define the settings for your container in the yaml file. Then save the yaml someplace safe to reuse the next time you want the same container - potentially built off a newer image.

I totally agree that there could be a great deal of user facing improvements made here

[vincent1890]

For info the solution has almost been found it is probably still to improved, but it normally avoids to recreate a container manually each time.
viewtopic.php?f=354&t=155736&p=760125#p760125