Jump to content

primeval_god

Members
  • Content Count

    290
  • Joined

  • Last visited

Community Reputation

40 Good

About primeval_god

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. While I dont know for sure how the docker isolation plays into things, i do know that underneath docker is using Cgroups to do its thing. Just an additional thought, while i know nothing about vmtouch, if it worked inside of a docker container that would enable using a version on top of another base os.
  2. Honestly i think you would find that it seems a lot more complex than it actually is. I am not certain exactly what the setup for your reverse proxy would but i believe that handling multiple tiers of subdomains in letsencrypt and duckdns is fairly easy to do. I believe you would want to backup the minio appdata folder and likely its docker template as well.
  3. Theoretically would the script be effective if it was run within a docker container (specifically a long running container that periodically invoked the script rather than spinning up a new container for each invocation)? If so then might it be possible to use the per-container swappiness settings of docker to achieve the above?
  4. To add a variable to a the docker page, and edit the container. At the bottom of the template page will be an option to "Add another Path, Port, Variable, Label or Device" select that. Make sure to select Variable from the drop down. Without my server in from of me I dont remember exactly how the fields are named but for the "Key" field you put the variable name MINIO_DOMAIN. If i understand the document that i linked above the Value will be the base domain of your server so probably xyz.duckdns.org. I assume what you mean here is that navigating to xyz.duckdns.org will take you to the Minio container's login page. The following is based on that assumption. If instead you meant that generically your server can be accessed at that url and minio specifically is accessed via a path or subdomain of that url then things would be slightly different. So far as the sub domains go I believe that you will use a sub domain on top of your current name to access the bucket. So if your server is currently accessible at xyz.duckdns.org then your bucket would be at nameofbucket.xyz.duckdns.org It may be that your reverse proxy will need to be configured to forward each bucket subdomain on to the minio server, though it may be possible to forward all subdomains of xyz.duckdns.org to minio.
  5. I want to preface this answer by saying that I had not even heard of vhost bucket creation until I read this question. A quick search online led me to this page https://docs.min.io/docs/minio-server-configuration-guide.html search for virtual-host-style to find the section on what you are looking for. It sounds like it can be enabled by setting the MINIO_DOMAIN environmental variable within the container, which can be done by adding the environmental variable to the Docker Template. That is the easy part, unfortunately if i understand the guide correctly vhost style means your application accesses minio via a domain name where the bucket id is a subdomain. To get this to work you probably also need a reverse proxy setup and an internet facing domain name rather than accessing minio via your server ip address. Thought you might be able to get away with some host file trickery on the synology similar to this https://stackoverflow.com/questions/19016553/add-subdomain-to-localhost-url
  6. Despite knowing this is true, nearly every single time I find myself on the Docker page I attempt to use the dropdown before a remember that its not there. Its such a minor annoyance I never thought to bring it up, but now that someone else has I second the motion.
  7. So installing an application directly on unRAID is almost never the correct thing to do. As you are seeing not only is unRAID slackware based, it is also stripped down to best suit its primary function as a NAS. Your first choice for running applications on unRAID should always be in a docker. If there isnt a community supported image available in CA, then the next best bet is searching Docker Hub for a decently documented image. Of course if a docker image is not available then VM is the next best solution. These days bare metal apps (most typically plugins) are reserved for things that require direct integration with he unRAID OS or UI.
  8. Glad to help and glad to hear your found something that works for you. I have used Syncthing myself for quite some time, though for a much different application. I have been really happy with Syncthing's performance.
  9. Right but docker should still allow you to do bind mounts to children of /sync such as /mnt/user/1_New -> /sync/1_New even if you dont have a /mnt/user -> /sync binding.
  10. Sort of but not exactly. My suggestion would be to just remove the direct binding to /sync altogether, and leave the bindings to the subfolders of sync the way you have them now. The only potential gotcha i can think of would be what if the application stores anything in the sync folder outside of the individual sync directories you map in.
  11. I am not quite sure i understand this. Assuming that what i first suggested works then it should be possible to only map the individual shares you need to sync (i.e. /mnt/user/3_Processed-> /sync/3_Processed) rather than map the entire array (i.e. /mnt/user -> /sync). Again its not really critical, I just wanted to make clear that i was suggesting mapping all shares individually and removing the blanket mapping.
  12. Just a quick note on your configuration above. Unless necessary its usually not recommended to map the entire array into a docker container (Host Path 2: /mnt/user -> /sync). Usually its preferable to give a container access to only the paths that it really needs, this improves security and lows the risk of an application accidentally touching files it shouldnt. With sync programs like RisilioSync it can be kind of a hassle to first map the individual directories you want to sync in docker and then select them in the applications, which is why some choose to just map everything.
  13. I assume Resilio sync is in a docker correct? If so you could add multiple bind mounts to your container as follows. /mnt/user/1_New -> /somepath/1_New /mnt/user/2_Import -> /somepath/2_Import /mnt/user/3_Processed-> /somepath/3_Processed then tell the resililo sync application to sync the directory /somepath/ If the app also stores state info in a hidden subfolder of the sync directory (such as /somepath/.resillio_sync) then you would also want to mount it into the container as well. example: /mnt/user/appdata/resillioSync/somepath/resillio_sync -> /somepath/.resillio_sync I have never used this app myself but i imagine this should work.
  14. Unfortunately so far as i am aware this is the best there is. When last i asked about how to get started creating plugins it was suggested that the best way is to look at the github repos of some of the more prolific plugin writers to see how they constructed their plugins.