Jump to content

Ikthayt

Members
  • Posts

    4
  • Joined

  • Last visited

Posts posted by Ikthayt

  1. 2 hours ago, Clifford B Brown said:

    They show an option on the Github page for "--security-opt seccomp=unconfined" that fixes this on the docker image. It's mentioned in some issues: https://github.com/linuxserver/docker-calibre/issues/97 and https://github.com/linuxserver/docker-calibre/issues/102.

     

    This fixes it for me on Unraid.

     

     

    For those trying to figure out how to add this extra variable to the docker template, you need to go to 'advanced' view (slider in the upper-right corner) and then look for the 'Extra parameters' section and enter this in the field:

    --security-opt seccomp=unconfined

     

    image.thumb.png.9552399bc33807fbfe34db9531fae302.png

     

    Worked for me as well - calibre gui back up and running.

    • Like 3
    • Thanks 3
    • Upvote 2
  2. On 3/16/2022 at 7:07 PM, silman said:

     

    Moving over is easy! You can delete all the other stuff in the appdata folder besides the 'data' folder (the folder containing Data, Logs, and Config dirs) and then just point your Game Data Path to that data folder. Then you can delete the fithwum docker (and image) and start up this one.

    I currently use the fithwum container and have two different mappings; one for the data (my worlds, uploads, modules, compendiums, etc.), one for the actual VTT software.  

    /foundry/data <--> /mnt/user/Foundry/
    /foundry/fvtt <--> /mnt/user/appdata/FoundryVTT

     

    Did this just to keep the appdata folder reasonable, as it is on the SSD cache array and my data folder is on the storage array (data folder is nearing 40GB at this point, so don't need all that on the cache).  The server running from the appdata folder is fine though.

     

     Thoughts?  I'm not totally stuck on this - just made sense at the time with fithwum's config. 

×
×
  • Create New...