I have several Kamal apps that I deploy together. I am splitting the build and deploy steps for a few reasons:

• Build all of the apps at the same time
• Run database migrations before deploying
• Trying to reduce the amount of time between deploys between dependent apps (web + api).

I'm using the kamal build deliver command during the build and kamal deploy --skip-push on the deploy steps. I thought that with --skip-push, if the image was already on the host, it would just bring up a container from the new image, and swap over to it. But this step took longer than I expected and when I looked I saw that it was removing the image and re-pulling it.

Run kamal deploy --skip-push --version="$KAMAL_VERSION"
Pull app image...
  INFO [2a748663] Running docker login ghcr.io -u [REDACTED] -p [REDACTED] on [REDACTED]
  INFO [2a748663] Finished in 1.425 seconds with exit status 0 (successful).
  INFO [dd554db8] Running docker image rm --force ghcr.io/shichongrui/rnl-graphql:bdbdfa39e851f0358e82a4407eb649c2da75c61f on matt-workstation.tail48e4b6.ts.net
  INFO [dd554db8] Finished in 1.428 seconds with exit status 0 (successful).
  INFO [1d394236] Running docker pull ghcr.io/shichongrui/rnl-graphql:bdbdfa39e851f0358e82a4407eb649c2da75c61f on matt-workstation.tail48e4b6.ts.net
  INFO [1d394236] Finished in 34.661 seconds with exit status 0 (successful).

It's not a huge deal but because I'm running kamal build deliver before hand, I don't need it to pull again. I can't find any flags for the deploy command to prevent it from pulling again but figured I'd ask in case someone knows something. Or perhaps there is a combination of other commands I could run that would have the same effect?

Thanks!