# Update within Docker container

**URL:** <https://community.doppler.com/t/update-within-docker-container/249>\
**Category:** Need Help\
**Created:** [July 5, 2021, 3:49pm UTC](https://community.doppler.com/t/update-within-docker-container/249 "2021-07-05T15:49:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![veverkap](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/veverkap/32/169_2.png) [@veverkap](https://community.doppler.com/u/veverkap)\
**Post date:** [July 5, 2021, 3:49pm UTC](https://community.doppler.com/t/update-within-docker-container/249/1 "2021-07-05T15:49:32Z")

</div>

I have a secret that will need to be updated within the course of running the Docker container - let’s call that REFRESH\_TOKEN.

When the docker container starts, we pass that in but inside the Node application, that REFRESH\_TOKEN will change. I want to update that when it happens, but since there is no Node SDK presently, I’d have to use the [API Reference](https://docs.doppler.com/reference#update-a-configs-secrets) method of the Doppler API, which I’m fine with. But to do that, I need to use my PERSONAL token, since Service Tokens are read-only.

Is the expected way of doing that to use a Personal Token? And I store that in the project secrets?

---

<div class="post-metadata">

**Author:** ![ryan-blunden](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/ryan-blunden/32/9_2.png) [@ryan-blunden](https://community.doppler.com/u/ryan-blunden)\
**Post date:** [July 6, 2021, 4:40am UTC](https://community.doppler.com/t/update-within-docker-container/249/2 "2021-07-06T04:40:28Z")

</div>

Hi @veverkap and welcome to the Doppler community!

Yes, personal tokens are designed specifically to be used with our API, and your approach of exposing it as a Doppler secret sounds good too.
