Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Unable to uninstall app followed by reboot unable to start

Unable to uninstall app followed by reboot unable to start

Scheduled Pinned Locked Moved Solved Support
troubleshootdisk space
2 Posts 1 Posters 36 Views 1 Watching
  • 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.
  • canadaduaneC Offline
    canadaduaneC Offline
    canadaduane
    wrote last edited by joseph
    #1

    I've been experimentally trying to create a Windmill for Cloudron container. However, I'm now stuck without the ability to uninstall it, and it has now taken down my whole server 🙃

    7391eba2-914f-42d5-aeec-0ca39fd4f366-image.png

    Here is how (I think) I got here:

    1. Windmill requires docker service, because it has an lsp container and worker containers that need to spin up during execution.
    2. I was trying to diagnose a failure to start, so I entered a cloudron console for windmill and ran the start.sh script that is normally reserved for booting up the Docker container.
    3. At this point, the console itself got stuck in a crash loop--it tried connecting, would fail, then would restart, restart, restart...
    4. I tried to uninstall the container itself, but that resulted in the error 500 above (with tantalizing "message:" and no message).
    5. I then rebooted the server itself, but it won't come up again.

    How do I get back to running state? What logs should I look for to find out why I can't boot?

    1 Reply Last reply
    1
    • canadaduaneC Offline
      canadaduaneC Offline
      canadaduane
      wrote last edited by
      #2

      Update: never mind. I ran out of disk space. Fixed by deleting the docker registry app that had been holding on to all of the docker data during experimentation.

      1 Reply Last reply
      4
      • J joseph has marked this topic as solved
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Bookmarks
      • Search