Unable to update from 0.9.52 to 0.9.70

[XiQshoner]

Hello Folks,

There are some updated miners that I would like to access in 0.9.70. When I run the auto update command it states I am on the best version @ 0.9.52...
The output I receive after running the auto update command

**2020-06-02 16:01:18,831 INFO:0.9.11 Current status:
2020-06-02 16:01:18,831 INFO:0.9.11 minemeld-engine: current: 0.9.52.post1 latest: 0.9.52.post1
2020-06-02 16:01:18,832 INFO:0.9.11 minemeld-webui: current: 0.9.52 latest: 0.9.52
2020-06-02 16:01:18,832 INFO:0.9.11 minemeld-prototypes: current: 0.9.52.post1 latest: 0.9.52.post1
2020-06-02 16:01:19,262 DEBUG:0.9.11 curl output:
2020-06-02 16:01:19,390 DEBUG:0.9.11 curl output:
2020-06-02 16:01:19,390 DEBUG:0.9.11 gpgv: /usr/bin/gpgv --ignore-time-conflict --keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d/minemeld.gpg /tmp/mmaupackagesgpg8W__86 /tmp/mmaupackagesp5rJjD
2020-06-02 16:01:19,396 INFO:0.9.11 gpgv output: gpgv: Signature made Tue 15 Jan 2019 02:52:41 AM EST using RSA key ID 7B630999
gpgv: Good signature from "Palo Alto Networks, MineMeld Team minemeld@paloaltonetworks.com"
gpgv: aka "[invalid image]"

2020-06-02 16:01:19,402 INFO:0.9.11 No package to deploy, exit**

[jtschichold]

Hi @XiQshoner,
could you tell which distribution are you using? You need at least Ubuntu 16.04 to receive recent updates.

[XiQshoner]

I am currently running 14.04.6LTS. Can I do an in place upgrade of the OS without wrecking my MineMeld instance?

[jtschichold]

Easiest path is exporting a backup of your MineMeld instance via the UI, install a new 16.04 instance and import the backup.
I have seen errors in python generated by the upgrade of 14.04 to 16.04.
Going forward you should also think of moving to the docker version of MineMeld.

[XiQshoner]

What is the benefit of going with Docker?

[jtschichold]

Easier to maintain and upgrade as all the dependencies are packed inside the container image.

[XiQshoner]

Thanks for the information. Feel free to close this out.