# Session affinity ("sticky sessions")?

**URL:** <https://community.fly.io/t/session-affinity-sticky-sessions/638>\
**Category:** General\
**Created:** [January 26, 2021, 8:00pm UTC](https://community.fly.io/t/session-affinity-sticky-sessions/638 "2021-01-26T20:00:30Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![kurt](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kurt/32/43757_2.png) [@kurt](https://community.fly.io/u/kurt)\
**Post date:** [January 26, 2021, 11:43pm UTC](https://community.fly.io/t/session-affinity-sticky-sessions/638/9 "2021-01-26T23:43:53Z")

</div>

Yes! `flyctl auth docker` does the Docker login for our registry, so if you have a build process somewhere that pushes to GCR, you could add a push to Fly step. You’d basically:

- `flyctl auth docker`
- `docker tag <image-ref> registry.fly.io/<fly-app-name>:latest`
- `docker push registry.fly.io/<fly-app-name>:latest`

I think that’s the right tag command. I never can remember.

Then: `flyctl deploy -i registry.fly.io/<fly-app-name>:latest`

---

_[View the full topic](https://community.fly.io/t/session-affinity-sticky-sessions/638)._
