issue update command from gui

[danmed]

it would be awesome (in my use case) the be able to issue an update command from the gui..

I have a lot of docker hosts spread over hosts and this would be a massive time save to me

[Palleri]

Im working on it, might not be possible right now.
Might need help how to implement it. I am looking at portainer and watchtower to see if I can figure out how to implement it in DCW.

[danmed]

Awesome.. i guess in reality it's a case of running through the process of..

• Stop container
• delete container
• delete images
• pull image
• start container with original parameters

Atleast that's how i handle it in my scripts i run.. it's likely not the most efficient method

[Palleri]

Yeah, that's it. On the other hand docker API cannot recreate the container so it has to start it with the original parameters exactly as you said. This makes it a little bit more complicated. This must work only with the help of docker.sock or docker API because it is running inside a container. I cannot/wont pass down the whole docker-compose file due to security reasons "password and secrets". I really appreciate your feedback. I would really like to see that script of yours if possible. Might give me more information on how to handle it.

[danmed]

It's just a shell script that i call from wget

Here's an example :

docker container stop portainer_agent
docker container rm portainer_agent
docker image prune -a -f
docker run -d \
  -p 9001:9001 \
  --name portainer_agent \
  --restart=always \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v /var/lib/docker/volumes:/var/lib/docker/volumes \
  portainer/agent:latest

[danmed]

Actually, by happenstance.. one of mu hosts crashed whilst i was updating a container via portainer and it seems the way they handle it is to rename the old container, then recreate it with the original name.. then i guess they delete the renamed one and start the new one.

[Palleri]

Yeah you are right.
I just have to figure out how to pass all the configurations of running containers to something like that shellscript of yours.
To see if all the configurations are following such as mounts, volumes, secrets and .envs.

[Palleri]

UPDATE:

I have a prototype for this now.
It is working but only for single containers and only on the MAIN_DCW host for now.
If there is multiple services in a docker-compose it will not work as intended.
It will still update the container but it will not work until you restart the entire container stack.

Use palleri/dcw:develop

Use at your own risk, it might be smart to test this on a host with a few containers you are not afraid to lose.

There is no warning when you press the update button beside a container, it will just run so be careful!

The script will preserve all the configurations from the old container. I say "all" becuase it should, but this might not be true.

I have tested this with Lazydocker to have a overview over the container being updated.
While having this open and used the Update button on the webpage.

When you press the button it will:

• save configurations of the selected container.
• remove the old container.
• pull the new image.
• start the new container with the new image and the old configurations.

This will take you back to the main page, press the check for updates button to see if the changes has been made.
When check for updates is finished the container should no longer be in the Containers with updates available: column

It should also preserve volumes and environment variables/files.
I need help to bugcheck this. Test it as hard as possible if you guys have time for it.

[danmed]

Hey man, sorry.. this is flipping awesome but i'm about to disappear for 3 weeks with the family on holiday so my keyboard warrior lifestyle has taken a serious back bench..

I'm loving your work i just cant offer any testing right now!

[Palleri]

Ye no worries.

There is alot of bugs with the develop image, it is not stable.
If you have your docker network setup in bridge mode it works great. I am using macvlan, and dedicated ip addresses on all my dockers. This script is missing those things out. I am trying to figure out how to make sure it saves all the conf from running containers and use them to start up the new one.