primeval_god
-
Posts
869 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by primeval_god
-
-
Its a cool idea, but unlikely to be helpful except for the rare case of actual bitrot. For things like overwrite, accidental deletion, corruption due to software error, etc. the parity drive will be of little to no help because unRAID maintains real-time parity. Any changes made to the file under normal operation are immediately reflected in parity.
-
7 hours ago, 007craft said:
Its been 2.5 years. Has anything new changed? I updated this plugin and I still dont see anything.
There are no plans to support compose stacks other than those created through the webui.
7 hours ago, 007craft said:All my files for Jitsi are in /mnt/disks/NVME/appdata/jitsi\github\docker-jitsi-meet but the Stack I made with this GUI is pointing to (/boot/config/plugins/compose.manager/projects/Jitsi) .Do I have to move all the files in there? This is on the boot stick tho.
The default location for stacks created via this plugin is on the flash drive. That default can be changed via the settings screen, or when creating a new stack there is an option to specify where it should be created.
7 hours ago, 007craft said:Maybe Im still confused as to what this plugin actually does?
This plugin provides a webui for people to create and manage simple compose stacks on unRAID. It exists primarily because unRAID's Dockerman lacks easy support for multi-container applications. It is not meant to be a full fledged, all features included compose interface. As such its not really geared for large, complex off the shelf compose projects you might want to pull down for github, but rather simple single compose file projects. For a full fledged compose experience i would recommend something like Portainer.
-
3 hours ago, Elmojo said:
So USB3 is okay? The docs say to use USB2 only. That would certainly make it easier to find a new drive... lol
There is nothing inherently wrong with USB3 flash drives that make them incompatible with unRAID. At one time (possibly still today) some motherboards had issues booting from USB3 drives but not from USB2 drives. I think those issues may have also included a tendency for the USB3 drive to drop offline periodically but dont quote me on that part. Additionally USB3 drives, particularly smaller form factor ones, tend to run much hotter than their USB2 counterparts, overtime that is probably not good for the flash memory. If those problems dont apply to your flash drive/mobo then a USB3 drive will likely work just fine.
-
2
-
-
4 hours ago, Napoleon said:
Saying it is intended to run with no exposure to the outside internet when there is quite literally an app store with hundred of apps to allow just that is a bit odd, don't you think?
The app store is not a built in component, it is community run and none of the apps are officially endorsed by unRAID. That said the important thing is that the unRAID host os not be exposed directly to the internet. Containerized apps are safer to expose (behind proper authentication) as they run isolated from the host os. The recommendation though has always been to use a VPN to access your home network and access all your services.
-
Can you see the files from the command line? If so the issue may be with permissions of the share and or the underlying data.
If the issue is permissions unRAID has a tool for correcting the permissions of your data. If you already have Docker apps setup the new permissions tool can cause issues, but there is a plugin (Fix Common Problems I think) that has a docker safe new permissions tool.
-
On 4/30/2024 at 7:21 PM, alucarddelta said:
Is there any documentation for these (plus any other) docker labels out side of forum posts?
Not that i am aware of. The icon, webui and shell are the only ones that I know of.
-
I preferred the orange text in the old dark mode. The text in the new dark mode feels to bright. The rest of the styling looks great though.
-
13 minutes ago, Thunderhead said:
Yeah but you can add it.
Not through any means that i am aware of. My point is, if wifi is something integral to your setup, you should not assume that it not working is a limitation of the trial. unRAID has never supported wifi officially or unofficially and its not on the roadmap, so I would not base a build on the assumption the you will be able to get it working.
-
46 minutes ago, Thunderhead said:
- Can't use Wifi even after added it (prob linked to the 1st one)
Wifi support is not a feature of unRAID.
-
On 4/24/2024 at 4:12 PM, Thunderhead said:
While I'm sure lots of people run it this way, I do a bunch of remote access and things that use internet access.
Having Docker containers and VMs that access the internet (but are not accessible from the internet) is generally fine, they are isolated from the host os to varying degrees. As for remote access the recommended way for unRAID is using a VPN into your home network as that is the most secure. Some people expose services in VMs and containers using a secured reverse proxy, which can be ok if you know what you are doing and are not exposing the unRAID host OS itself.
-
Personally I achieve this with the user.scripts plugin. I have scripts that run on a schedule that execute docker pause and resume commands.
-
45 minutes ago, Thunderhead said:
Maybe I could do without some new feature updates and MAYBE do without some security updates for a bit, but would my Plugins and Dockers still get updates from the Apps page? Wouldn't that inevitably lead to Plugins and Dockers being incompatible with the older OS as time goes forward?
Keep in mind that the "Apps Page" is actually a third party plugin called community applications (though it is developed more closely with Limetech than most). It acts as a convenient way to discover and install containers and plugins but it is not the only way to do so.
Also speaking from personal experience I have in the past typically not run the latest version of unRAID (I usually stay a version back). The lack of security updates for older versions (which was how it used to work before the licensing change) was rarely something that concerned me. unRAID is designed to run from within a home network, with minimal exposure to the outside world.
-
4 hours ago, Napoleon said:
Personally, I think its unreasonable to hold the security of our systems hostage to a subscription. This is an OS, security should be a priority.
This is a NAS appliance OS security has never been a priority. Ok thats not entirely true (said mostly for effect) but the fact is that the unRAID OS has always been slow to get security updates (except for the occasional critical issue), has a fairly lax security model, and is intended to run on a home network with no exposure to the outside internet.
4 hours ago, Napoleon said:Truenas, Proxmox, Xigma, Snapraid and OMV are all free for consumers, some with higher prices for the enterprise sector.
unRAID is a consumer product only with no enterprise level.
-
4 hours ago, csimpson said:
Not really, I just didn't know if the cache drive was tied to the parity drive at all. Almost like if I have the 8TB parity, two 4TB spinning discs and then another 120GB SSD, would the entire array be 8,120TB including the SSD.
The term "Array" is old nomenclature that refers to the singular required drive pool that uses the unRAID's proprietary unRAID scheme. The "Array" pool can contain mixed drive sizes and types (though mixing SSDs and HDDs in not recommended), as well as up to 2 parity drives to maintain redundancy for the pool. unRAID also supports optional secondary drive pools (previously called cache, but weren't a cache in a typically sense of the word). These secondary pools can be single disks or have redundancy via ZFS or BTRFS software raid levels. These secondary pools are separate from the "Array" pools in terms of redundancy. In terms of file access unRAID has user shares which preset a combined view of folders from all the various drive pools. There are options to set which pool data gets written to when writing to a user share and when and if data gets moved between pools. One common usage of this is to direct all writes to an SSD pool and then have unRAID move the files onto the Array pool later.
Finally to the point above, the general recommendation is to have an SSD based pool to store appdata on, separate from the Array. Whether or not the pool used to store appdata has redundancy is up to you but it does not effect the configuration of the "Array" pool. -
17 hours ago, AngryPig said:
That's good to know. Are they required to be in a Subvolume for Send to work or because they are Subvolumes themselves they will automatically work with Send?
Yes send and receive work on subvolumes only (snapshots are just a type of subvolume).
17 hours ago, AngryPig said:Thank you for clarifying this. Does the other file system have to BTRFS to be able to Send to it? ie I would not be able to send to my array as it is XFS?
Yes the other filesystem has to be BTRFS for send and receive to work, the send subvolume becomes a subvolume on the receiving filesystem.
17 hours ago, AngryPig said:Does this plugin allow for me to Snap on a daily basis and Send on a weekly basis?
I am not entirely sure about the capabilities of this plugin with regards to scheduling.
17 hours ago, AngryPig said:So if I was Sending off-site it would not use my bandwidth as much? Or is it simply that since it maintains the BTRFS CoW, it would not be that much bandwidth after the initial send?
BTRFS send and receive does a sort of differential send when subvolume/snapshot is based on subvolume/snapshot that is present in both filesystems (assuming you use the option to specify the parent). This reduces the amount of data sent for subsequent snapshots of the same subvolume. I am not sure if this plugin actually makes that option available though as I do my snapshot sending via the command line.
-
1
-
-
14 hours ago, AngryPig said:
This will convert that share to a subvolume. Since this is a file system level of change, do I need to go in and update Docker mappings and the Share Settings (Primary storage, move settings, SMB settings etc) as if a new Share had been created in UNRAID? Or do I now have two Shares of the same name and I need to configure the new one and remove the old one?
You will want to stop any Docker containers that have a mapping to or within the share you are operating on while you make changes, aside from that though you dont need to make any changes since you are creating the subvolume with the original path. Likewise you shouldnt need to make any changes to share settings since so far as unRAID is concerned the new subvolume (which has the same path as the original user share) is the existing user share.
15 hours ago, AngryPig said:I can then enable Snapshots of a Subvolume and either store it within the Subvolume (preferred?) or to a different Subvolume as long as it is on the same pool. ie I cannot make a snap to /mnt/cache-single/some-snaps as 'some-snaps' is not a Subvolume
Where you store snapshots doesnt really matter, they can be anywhere within the same pool (they dont have to be within a subvolume). Snapshots themselves are just subvolumes anyway.
15 hours ago, AngryPig said:I cannot send to /mnt/cache-double/... as 'cache-double' is a different pool.
This is not entirely true but it requires some explanation. When you snapshot a subvolume the snapshot must be made somewhere on the same filesystem (pool) as it is a CoW copy of the subvolume (and a new subvolume itself). You can however send subvolumes from one BTRFS filesystem to another using btrfs send and receive (which are available in this plugin). Doing this copies the subvolume to the other filesystem and thus it is no longer CoW copy but a full copy taking up space on the other filesystem. Once a subvolume is sent to the other filesystem there is a way to send subsequent snapshots of that subvolume between the two filesystems in a way that maintains the CoW relationship between the subvolume and its snapshots.
-
1
-
-
4 hours ago, unraid_fk34 said:
So I'm having issues displaying the custom network name in the docker containers tab. It will only show me the ID. I found a thread discussing this particular issue on the forums. Is that something that has to do with unraid or the plugin? Is it something that could be fixed in the future or is there a solution maybe?
The issue is with unRAID not this plugin. Last I was aware there was an open PR fixing the issue.
-
10 hours ago, kiwijunglist said:
This doesn't seem to be available anymore under community apps.
I installed using docker-compose-manager plugin.
Add new stack, name it vorta.
Is there a question here? I dont really understand the post.
-
5 hours ago, Lebowski89 said:
Getting some label UI oddities here and there. For example, with Traefik, I've put the correct URL (http://192.168.##.##:port) in the Web UI column but it opens the localhost IP without a port. Then for Whisparr the WebUI is also correct, but when you open it the IP you've entered is doubled (http://192.168.##.##/192.168.##.##:port). Have tried stack down, up, updated, deleted containers, etc.
The changes you are making are likely not taking effect. There is a long standing issue with how dockerman handles the webui and icon labels. Basically it caches them the first time a container is seen and subsequent changes dont have an effect. Try restarting your server, that may fix the webui label issues.
-
1
-
-
7 hours ago, Lebowski89 said:
I notice only .png are working for the icons. Using an .svg displays a blank icon. This differs from Docker Folders which accepts both. Is this intentional?
That is a Dockerman question. The compose plugin only assigns the labels to the containers. Unraid's builtin Dockerman is what actually reads the label and caches/displays the icon.
-
1
-
-
On 3/20/2024 at 5:23 PM, mbush78 said:
Are we like the only weird-o's that were building docker images in unraid?
Or are we just to only two that somehow broke their system lol.
I haven't tried it yet but was thinking maybe I'll create a fresh install of the trial build on some random usb stick just to see if buildx works there and it's really just my issue or if its truly busted 😕 really dunno what else to do. Is there someplace to submit bug tickets that I've totally overlooked somewhere?
I was blind, https://account.unraid.net/troubleshoot going there allowed me to submit a support ticket.
Did you get any response on your support ticket?
-
2 hours ago, TRusselo said:
Reading through the forums over the past 7 years I know I'm not the only one that this happens to
Still having that flash drives fail with that frequency is not normal. It suggests some sort of hardware or configuration problem. Do you notice continual writes to your flash?
-
Is this a container run via unRAID's built in Dockerman interface or by some other method?
-
Other options for installing things are via virtual machines, or LXC containers (using the lxc plugin)
Or are we just to only two that somehow broke their system lol.
[Plugin] Docker Compose Manager
in Plugin Support
Posted
Just ignore the "update ready" text for containers created via compose, they are not correct. The update tracking feature of the webui does not apply to containers not created via the webui. If you believe there is an update available for a container created with the compose plugin, there is an update stack button on the compose page you can click.