Accessory reboot with fresh image

[miharekar]

kamal accessory reboot [name] currently stops, prunes, and re-runs the image.

The only way to update the image is to log in to server and do a docker pull [image-name]:latest followed by kamal accessory reboot [name] and that will run the newest version of the container image.

It would be great if we could pass an option to reboot - like --pull or something, or have a new command to refresh the accessory container image.

WDYT?

[hundredwatt]

I added an alias to make it more convenient to pull the latest image, but agree this should be a configuration option or command for the accessory

aliases:
  pull-<accessory>: server exec docker pull <image>:latest

Then I can do:

kamal pull-<accessory>
kamal accessory reboot <accessory>

[jeremy]

The only way to update the image is to log in to server and do a docker pull [image-name]:latest

Deploying the app also pulls the accessory image, yeah?

[miharekar]

Does it? Huh, didn't know. Well if that's the case it should do the same on accessory reboot, right?

[hundredwatt]

No, kamal deploy does not touch accessories at all. kamal setup calls accessory boot, but that fails if the accessory is already running

[jeremy]

Indeed! My bad. Only way is to use specific tags then, huh, rather than latest.

It would be interesting if Kamal::Commands::Accessory#run used --pull by default. But it'd be surprising if a reboot did an upgrade.

[miharekar]

This is especially confusing since kamal proxy reboot does pull a fresh image and restarts 😅

[nickhammond]

The alternative is to always use a more specific tag with your image instead of latest, then when you need to update it'll have to pull the new tag. A specific tag(v1.1.4) is also more predictable than latest since you know your application works with that version and doesn't pull in a major upgrade.