# Migration / update problem new SSD

**URL:** https://discuss.tryton.org/t/migration-update-problem-new-ssd/3197
**Category:** System Administrator
**Created:** [September 8, 2020, 5:08pm UTC](https://discuss.tryton.org/t/migration-update-problem-new-ssd/3197 "2020-09-08T17:08:05Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![edbo](https://discuss-cdn.tryton.org/letter_avatar_proxy/v4/letter/e/f14d63/32.png) [@edbo](https://discuss.tryton.org/u/edbo)
#### Post date: [September 8, 2020, 6:06pm UTC](https://discuss.tryton.org/t/migration-update-problem-new-ssd/3197/2 "2020-09-08T18:06:08Z")

</div>

> [@herrdeh](#):
>
> - Can the above error be resolved easily ?

I thinks this is the same issue as in [Migration 5.4 \> 5.6, sqldump import](https://discuss.tryton.org/t/migration-5-4-5-6-sqldump-import/3184) It seems you forgot to manually update the database with `trytond-admin`

> [@herrdeh](#):
>
> - What is the recommended strategy to move and existing tryton docker to another machine?

Just copy-and-paste? 😉 … they call it a container so it should be easy to move. In practice it’s more complicated. As I’m not using Docker but Python virtual environments I cannot help you further with this, but [How to Transfer/Move a Docker Image to Another System? - Gcore](https://appfleet.com/blog/how-to-transfer-move-a-docker-image-to-another-system/) can maybe help you.

> [@herrdeh](#):
>
> PS: At the first glance, the docker solution looked promising. But after some time of dealing with it I get the impression that you really should have some experience with docker if you want to use it with tryton. Tryton is not so easy - but docker adds another thick layer of complexity… ):

Indeed Docker adds an extra layer of complexity and for me it doesn’t give me any extra’s. I’m using Python virtual environments and are up-and-running in minutes. Installing extra modules is a `pip install` away. The same for updating Tryton. When I want to dig into the database I don’t need to enter docker-commands etc. Once you have a good working environment you do a `pip freeze > requirements.txt` which spits out all the packages you have. The main reason to use a Python virtual environment is to keep the original ecosystem clean. When you messed up things, you throw it away and start again.

You are on Ubuntu and if you know your way around with the commandline a bit IMO it’s easier to setup Tryton with a virtual environment than using Docker.

---

_[View the full topic](https://discuss.tryton.org/t/migration-update-problem-new-ssd/3197)._