Difference between revisions of "How to upgrade umbrel without upgrading umbrel"

From PlebNet Wiki
Jump to navigation Jump to search
Line 17: Line 17:
'''tor proxy'''
'''tor proxy'''


<code> cd ~/umbrel; docker pull docker pull lncm/tor:0.4.7.8</code>
<code> cd ~/umbrel; docker pull lncm/tor:0.4.7.8</code>


Do note the digest for each docker image you pull. It would look as below. It is best to copy-paste into a notepad since you will need that information later.  
Do note the digest for each docker image you pull. It would look as below. It is best to copy-paste into a notepad since you will need that information later.  
Line 25: Line 25:


'''bitcoind'''
'''bitcoind'''
<code>cd ~/umbrel; docker pull docker pull lncm/bitcoind:v23.0</code>
<code>cd ~/umbrel; docker pull lncm/bitcoind:v23.0</code>


'''lnd'''
'''lnd'''
<code>cd ~/umbrel; docker pull docker pull lightninglabs/lnd:v0.15.0-beta</code>
<code>cd ~/umbrel; docker pull lightninglabs/lnd:v0.15.0-beta</code>





Revision as of 22:10, 8 July 2022

After the recent upgrade of umbrel to 0.5, bitcoin and lightning have been moved to app structure and this has broken existing scripts and tooling for many node runners. If you would like to remain on the lower version of umbrel but want to take advantage of the newer release of lnd/tor/bitcoind and other apps you can try the following AT YOUR OWN RISK. The steps below require editing docker-compose.yml files on your umbrel node to use latest release of the underlying software.

WARNING EDITING THESE FILES ARE RISKY AND SHOULD ONLY BE ATTEMPTED BY THOSE WHO ARE COMFORTABLE WITH SSH AND FAMILIAR WITH DEBUGGING THEIR NODE IN CASE THINGS GO WRONG. YOUR EDITS WILL BE REPLACED BY NEWER UMBREL UPGRADE WHICH CAN HAVE UNWARRANTED CONSEQUENCES.

If you still wish to proceed after this the rest of the procedure is simple.


Step 1. Make copy of your docker-compose.yml cd ~/umbrel; cp docker-compose.yml ~/docker-compose.yml.bak

In case of issues, this will be used for reverting the system to original state.


Step 2. Download the latest binaries for the subsystems you wish you upgrade. The version mentioned in the commands below needs to be updated for the latest image.

tor proxy

cd ~/umbrel; docker pull lncm/tor:0.4.7.8

Do note the digest for each docker image you pull. It would look as below. It is best to copy-paste into a notepad since you will need that information later.

0.4.7.8: Pulling from lncm/tor Digest: sha256:aab30ebb496aa25934d6096951d8b200347c3c3ce5db3493695229efa2601f7b

bitcoind cd ~/umbrel; docker pull lncm/bitcoind:v23.0

lnd cd ~/umbrel; docker pull lightninglabs/lnd:v0.15.0-beta


Step 3. Edit the docker-compose.yml file with the latest images

cd ~/umbrel; nano docker-compose.yml

yml files need careful editing since they do not tolerate unwanted characters. Please be careful.

for each of the image to be updated, edit the yml file with the imagename@sha256 hash you got from the digest. For example


tor proxy

       tor_proxy:
                container_name: tor
                image: lncm/tor:0.4.7.8@sha256:aab30ebb496aa25934d6096951d8b200347c3c3ce5db3493695229efa2601f7b


bitcoind

       bitcoin:
                container_name: bitcoin
                image: lncm/bitcoind:v23.0@sha256:57317c90d89156a30327fe1b8e51b836e0fd1a8ba13721eb2e75e6b35a570e26


lnd

        lnd:
                container_name: lnd
                image: lightninglabs/lnd:v0.15.0-beta@sha256:d227a9db0727ff56020c8d6604c8c369757123d238ab6ce679579c2dd0d0d259


Step 4 : Restart

cd ~/umbrel; sudo scripts/stop && sudo scripts/start

Step 5 : Validate from logs that the latest version is being used. Done!