• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
MagicMirror Forum
  • Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.

MagicMirrorOS build intermittently not starting mm container (Version 2.30)

Scheduled Pinned Locked Moved Solved Troubleshooting
23 Posts 3 Posters 2.0k Views 3 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    scottwalsh @karsten13
    last edited by Feb 14, 2025, 12:09 AM

    @karsten13 said in MagicMirrorOS build intermittently not starting mm container (Version 2.30):

    the script /opt/mm/install/install.sh is executed with every reboot.

    As workaround you could add

    Is that executed on the OS boot, or by one of the containers as they start?

    I was thinking of a workaround like that to introduce a pause. Given the low machine spec, it seems to be busy for about 5min after sshd starts, so will just try a 300 sec sleep.

    K 1 Reply Last reply Feb 14, 2025, 5:32 PM Reply Quote 0
    • K Offline
      karsten13 @scottwalsh
      last edited by Feb 14, 2025, 5:32 PM

      @scottwalsh

      on OS boot

      1 Reply Last reply Reply Quote 0
      • S Offline
        scottwalsh
        last edited by Feb 17, 2025, 5:55 PM

        As an update, based on the pointers from @KARSTEN13 and @SDETWEIL, have a workaround.

        Had three issues going on.

        1:
        I found that on a graceful reboot (shutdown -r now) that it would generally start fine, but not on an ungraceful reboot (power cycle the machine).

        Looks like when it was ungraceful reboot, the labwc container would show with uptime of (for example) five hours when ‘docker ps’, even though the machine was rebooted 20min ago after ‘docker compose up’ was executed by install.sh. Whereas the magicmirror container would have recently started.

        I assume kind of lock file confusing things?

        Workaround was to change the first ‘docker compose up’ install.sh to ‘docker compose up -d --force-recreate’

        2:
        I’d also included a pause and --force-recreate at the end of the install.sh and noted it was never executing as per @KARSTEN13’s suggestion.
        Looked like the install.sh script was hanging at docker compose pull.
        Commented that out.

        3:
        Lastly, the initial ‘docker compose up -d --force-recreate’ in install.sh would still fail often with the mm container restarting with logs as per the original post.

        With a 7 min pause and then second ‘docker compose up -d --force-recreate’ it seems to start the second time well (3min wasn’t enough, 5min was better, 7min seems to work).

        Workaround is a bit on the slow side, at some point will see if can refactor it a bit so that a pull for updates occurs.

        Extract of resulting install.sh below.

        _info "--> Pulling docker images and starting magicmirror"
        # need sudo for docker here if docker was installed with this script
        
        # use up so mm can start if there are already local images
        _info "--> Pre Start Pause for 2min"
        sleep 120
        
        _info "--> Start and recreate"
        $_sudo docker compose up -d --force-recreate
        
        #_info "--> Pull Pause for 1 min"
        #sleep 60
        # pull new images
        #_info "--> Image Pull"
        #$_sudo docker compose pull
        
        #_info "--> Restart Pause for 1 min"
        #sleep 60
        # restart (only if new images pulled)
        #_info "--> Restart stopped"
        #$_sudo docker compose up -d
        
        _info "--> Final Pause for 7 min"
        sleep 720
        
        _info "--> Final  start and recreate"
        $_sudo docker compose up -d --force-recreate
        
        if [[ "$_sudo" == "sudo" ]]; then
          _info "--> Reboot needed, starting in 120 sec. (use ctrl-c to skip)"
          sleep 120
          sudo reboot now
        fi
        
        # cleanup
        $_sudo docker image prune -f
        
        1 Reply Last reply Reply Quote 1
        • S sdetweil has marked this topic as solved on Feb 20, 2025, 10:34 PM
        • S smegbadger referenced this topic on Apr 14, 2025, 7:06 PM
        • 1
        • 2
        • 3
        • 3 / 3
        3 / 3
        • First post
          23/23
          Last post
        Enjoying MagicMirror? Please consider a donation!
        MagicMirror created by Michael Teeuw.
        Forum managed by Sam, technical setup by Karsten.
        This forum is using NodeBB as its core | Contributors
        Contact | Privacy Policy