Results 1 to 2 of 2

Thread: do-release-upgrade fails cryptically without snapd

  1. #1
    Join Date
    May 2021

    do-release-upgrade fails cryptically without snapd

    I updated my 20.10 server to 21.04 and had to solve a problem along the way.

    I minimize the attack surface on this VM server machine by running only what I know I need. I run snaps only within VMs so I disabled snapd on the base machine.

    Turns out that the do-release-upgrade installer assumes snapd is available. Failure signature is:
    -- 0:hirsute -- time-stamp -- May/11/21 21:34:25 --

    Restoring original system state


    Googling revealed a bug report from a prior release upgrade that found snapd absence caused a silent abort. The bug was rejected.

    Enabling and starting snapd cleared the problem.

    Posting in case someone else encounters a similar issue.
    Last edited by deadflowr; May 12th, 2021 at 09:14 PM. Reason: fixed formatting, placed in quote tags

  2. #2
    Join Date
    Mar 2010

    Re: do-release-upgrade fails cryptically without snapd

    Thanks for the post. Time to make a decision about the OS our servers use, I suppose.

Tags for this Thread


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts