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. App Packaging & Development
  3. How do I know which docker bind mount is problematic for docker?

How do I know which docker bind mount is problematic for docker?

Scheduled Pinned Locked Moved App Packaging & Development
4 Posts 3 Posters 740 Views 3 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.
  • R Offline
    R Offline
    random_eric
    App Dev
    wrote on last edited by
    #1

    Hi,

    I'm trying to setup the woodpecker-ci on my cloudron system. The server portion is working fine but I keep getting this error in woodpecker:
    {"level":"warn","repo":"cloudron/woodpecker-ci","build":"8","id":"22","error":"rpc error: code = Unknown desc = Proc finished with exitcode 1, Error response from daemon: {\"status\":\"Bad Request\",\"message\":\"Binds must be under /app/data/\"}","time":"2022-10-22T15:02:14Z","message":"cancel signal received"}\

    The message is perfectly clear, but since I don't know very much about the inner workings of woodpecker, I actually don't know which volume it's trying to mount. Is there a way to find out it's trying to bind mount so that I can fix it?

    1 Reply Last reply
    0
    • nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote on last edited by
      #2

      Assuming you use the Cloudron docker addon, given the error message, you should see some logs about this in the system logs/box.log file mentioning Original bind mounts following the mount details.

      R 1 Reply Last reply
      0
      • R random_eric marked this topic as a question on
      • R random_eric has marked this topic as solved on
      • nebulonN nebulon

        Assuming you use the Cloudron docker addon, given the error message, you should see some logs about this in the system logs/box.log file mentioning Original bind mounts following the mount details.

        R Offline
        R Offline
        random_eric
        App Dev
        wrote on last edited by
        #3

        @nebulon Thanks! I found what I was looking for in the logs.

        It looks like it created a volume and then tried to mount it,

         Original bind mounts: [ '0_3474360222739265561_default:/woodpecker' ]
        

        Would it be possible to allow docker volumes created in that docker context to be mounted?

        1 Reply Last reply
        0
        • R random_eric has marked this topic as unsolved on
        • R random_eric referenced this topic on
        • girishG girish marked this topic as a regular topic on
        • S Offline
          S Offline
          Santoz
          wrote on last edited by Santoz
          #4

          It is not difficult to find the problematic docker if you look at the log. You can also use a monitoring service https://www.host-tracker.com/en that will detect problems automatically and notify you.

          1 Reply Last reply
          0
          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