> For the complete documentation index, see [llms.txt](https://docker.guides.coticommunity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docker.guides.coticommunity.com/installing-the-coti-node/upgrading-your-node.md). # Upgrading Your Node When Coti release new versions of their software, it is important to keep your node up to date, especially if your node is on the testnet, so that the new software can be tested before being rolled out to mainnet. Fortunately with Docker, upgrading is simple. ## Upgrading to the Latest Version If you didn't choose a version in your `.env` file, the Coti node can be upgraded with ```bash docker-compose up -d ``` This tells Docker to re-launch your node. In the process of re-launching, Docker check Dockerhub to make sure it has the latest version, and it downloads a newer version if one is available. The `-d` flag tells Docker to run the container in "detached mode", which means that the terminal will be freed from the container once it is launched. ## Upgrading (or Downgrading) to a Specific Version If you chose a version in your `.env` file using the `VERSION` environment variable, you should edit the version number in your `.env` file before relaunching the node. After changing the version number in the `.env` file, upgrading/downgrading can be done with the same command: ```bash docker-compose up -d ``` ## Summary If you have followed the guide this far, you now know everything you need to run your node with Docker! Make sure to pass the favour on by helping others set up their nodes, and stay active within the community. Thanks for reading. A list of useful `docker` and `docker-compose` commands is kept at the end of this guide, that you can turn to if you ever need to perform tasks that are not covered earlier in the guide. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docker.guides.coticommunity.com/installing-the-coti-node/upgrading-your-node.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.