primeval_god

Community Developer
 View Profile  See their activity

  • Posts

    854

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Everything posted by primeval_god

  1. primeval_god
    This is technically an issue with unRAID's dockerman rather than this plugin. The compose plugin does have a feature to patch this behavior along with a few other webui integration issues. It can be enabled in the settings but is disabled by default. Be sure you have the latest version of the plugin (released today) as there was a minor change to that functionality. Also FYI the webui patches will disable the update link in the main docker page for containers managed by compose.
  2. primeval_god
    @SCSI @Hendrik112 @elzik There is a new version that should fix the update function.
  3. primeval_god
    I would highly recommend running veracrypt as a docker container rather than trying to get a native package.
  4. primeval_god
    But why though? Part of the beauty of the unRAID array is that you dont need matching drives. You could upgrade your parity disks and 1 data disk (one disk at a time to maintain array integrity during the upgrade) and have and extra 10TB in the array. Then when you start to run low on space, or when one of the older drives starts to act up you can swap out another.
  5. primeval_god
    @SCSI@Hendrik112 I am aware of this issue and working on a fix.
  6. primeval_god
    This thread really isnt the place to ask general questions about docker compose. Please try to keep things focused on the compose plugin itself.
  7. primeval_god
    Are you using the default compose.manager directory for your stack or did you use the Advanced option to specify the Stack Directory? If you used the default directory then the above bit could be your issue. You should not put build files in the default stack directory. You should either put the whole stack directory somewhere else of put the build files somewhere else and specify an absolute path the context.
  8. primeval_god
    The webui button "Update Stack" is what you are looking for.
  9. primeval_god
    @benfishbus A new version of the plugin is available which I believe will solve your issue.
  10. primeval_god
    No need for that.
  11. primeval_god
    @benfishbus Do you happen to have the unassigned devices plugin installed?
  12. primeval_god
    Maybe its something that changed in the latest release. All 4 themes seem to render properly on 6.9.3. I will have to look at what has changed in other plugins. It may look strange but thats what its meant to look like. Thats not it at all. I have 0 web design experience, the interface you see here is cobbled together from bits of other plugins.
  13. primeval_god
    I am unable to reproduce this issue locally. It is true that the popups are not themed, but they look fine to me when running the black theme. What version of unRAID are you using?
  14. primeval_god
    Try using an online xml validator on your plugin source. I had a similar issue with a plugin I maintain. I dont know anything for sure but it seems like they may have tightened up the XML validation for the .plg. For me I needed to use a XML escape character in place of a character in one of my inline bash scripts.
  15. primeval_god
  16. primeval_god
    This is not a safe or recommended environment for unRAID.
  17. primeval_god
    Use docker compose ls to list all running stacks. The NAME column has the "project" name that was used to create the stack.
  18. primeval_god
    No problem, one last thing to be aware of is that the docker hub page has some bolded text regarding what to expect in terms of security. Make of that what you will.
  19. primeval_god
    I think veracrypt has a umask (or some similar name) option in its mount prompt. Try 000 for that. Also make sure the host path is under a properly shared user share.
  20. primeval_god
    If you look at the usage section on the docker hub page you will see a bind mount that looks like this -v </path/to/mount/images>:"/mnt/disks":shared \ The shared flag is very important its what allows the mount points to propagate to the host. In this case /mnt/disks is in the container and path/to/mount/images is on the host. When you mount your images in the docker container you must mount them to a mount point (subfolder) inside /mnt/disks. The mounted directory will be under path/to/mount/images on the host.
  21. primeval_god
    It would likely depend on exactly what shell commands you are exposing via that app, and what you are doing with them. But this sounds like a bit more complex set of automations than most.
  22. primeval_god
    An alternative is to just run the veracrypt gui in a docker container. https://hub.docker.com/r/dcflachs/veracrypt-gui
  23. primeval_god
    Dont. Unless it is explicitly required as the dependency of something else i would recommend not installing python on unRAID. Instead you should run your python scripts inside of a docker image. Once you understand the basics of Docker its much easier than it seems at first. It adds a bit of overhead but makes it much easier to manager python environments. See my comment in the linked thread for specifics.
  24. primeval_god
    Well thats just great... here i am thinking i am making a fix and really i am going backwards.
  25. primeval_god
    https://superuser.com/questions/12972/how-can-you-see-the-actual-hard-link-by-ls You can look at the output of ls and for each file determine if there are multiple hardlinks (including the one you are looking at) to the data.