primeval_god

SMR disks perform poorly in RAID arrays (including the unRAID array). If i remember correctly Drive Bender is not actually RAID, it used disk pooling and some sort of file level redundancy.

The icon label is typically a web address, i am not sure if unRAID supports specifying local icons. If it does the path would certainly need to be an absolute path. Note also that any changes you make to the label now will not change the icon because of the way Dockerman caches icons. I believe there are one or more earlier posts in this thread that describe how to manually remove the cached icon.

You cant. It is a limitation of the way unRAID's Dockerman displays networks. It will hopefully be fixed in a coming release of unRAID.

If you mean for the containers managed by compose then no. The compose manager plugin does not currently support update checks.

There is nothing special required to update the compose manager plugin. The update button on unRAID's Plugins page is all that is required.

Any chance you could share the compose file?

Just to be absolutely clear your existing license is still good and still entitles you to future updates. Nothing has changed about that, its just that it is no longer an option for new users to purchase that type of license. The option also still exists to update your existing "legacy" Plus license to a "legacy" Pro licensee if you need more drives.

You cannot make use of that file. It is generally not possible to manually upgrade the application within the docker container. From our perspective as unRAID users its best to think of the container as the application. We get updates when the maintainer (of the container not the application) pushes a new container version, or in the less common case of a container with a builtin update mechanism, when the container is restarted. If you are using the lsio version of the plex container you might try restarting it to see if it updates (not sure if theirs still does that or not). TLDR just because plex has an updated version does not mean that the particular plex container your are using is available with that update and there is not much to be done about it.

I assume Duplicacy is running in a Docker container. What are the permissions on the bind mount that the container uses to access the directory where Unassigned Devices mounts drives? It probably needs to be to some variant of "shared".

Please enable the "Debug Logging" option under "Settings/Compose". Then retry the failed command while watching the system log. Then you can post either the relevant lines from the log or your diagnostics.

Thats what it should look like.

What does your webui label look like and have you changed it since the first time you started the stack?

Basic profile support already exists. If your stack has profiles defined then the up/down buttons should appear with dropdown arrows that let you select a profile to target. Clicking the button itself will still execute the base command without a specified profile.

The whole reason for adding Docker in the first place was in support of keeping the core unRAID OS focused on its NAS duties. The idea being that any app the user decides they have to install, that is not built into the core OS, should be isolated. Using docker, non-core functionality, whether backup, media serving, or whatever else, can be run with resource limits, restricted access to specific files/folders, and minimal dependence on the host os. No need to worry about what version of Slackware unRAID is based on and what packages are available/included in it if your application has all of its dependencies bundled in a convenient container image.

Unfortunately this is likely not possible. The issue is that, to my knowledge, docker container registries do not provide an endpoint specifically for publishing changelogs. While the dockerman template system might provide such a feature it is not likely to be widely used as by and large templates available in CA are not officially maintained by the apps creators, or even the people who provide the docker container.

Unlikely to be anything specific to the unRAID OS. Its possible that it is meant for a different version of the docker engine than unRAID has installed. What version of unRAID are your running (and more to the point what version of the Docker engine does it contain). What version of the docker engine do you have in Docker desktop?

Also worth noting docker has an option to specify container labels via a file using the option --label-file. It can be specified in Dockerman's extra arguments field.

I dont think docker on unRAID uses the authz plugin

Thanks but I believe I understand the issue at this point. The underlying problem is very similar to the issue with how dockerman displays networks for compose containers. It appears that dockerman uses the "NetworkMode" property somehow to decide whether it should attempt to rewrite the webui url. Recent versions of compose set this property differently (depending on network configuration) than dockerman does. @mtongnz has a pull request open against the unRAID webgui repo that addresses the network display issue. Perhaps they would be willing and able to look into patching this issue as well.

Custom networks can be macvlan, ipvlan, and bridge type.

@Mihle This thread is for discussing issues with the compose plugin, not for supporting/discussing specific compose stacks.

It would be interesting to know what kind of network bond0.43 is. Also whether the issue happens if the network (of the same type as bond0.43) is not external (i.e. created when the compose stack is brought up). Unfortunately at this point a fix is likely out of my hands. The issue is something about the way Dockerman tries to extract the IP and PORT information from the container in order to re-write the url. For some reason it is not playing nicely with the way compose is attaching the network to the container. I suspect it may be related to the issue where dockerman doesnt display network names for containers created by compose but i am not certain. regardless any fixes will have to be made in dockerman.

As a test try removing the connection to the external bond043 network (compose will create a network for the container).

Yeah this plugin is really designed for simple, single compose file, single env file stacks created via its webui. Stacks that are pulled from elsewhere can quickly start to get more complex than this plugin was designed for.

Is the usb drive a portable type with just a USB plug or does it have a power adapter with it. If it is the portable type perhaps your minipc does not supply enough power for both usb devices. You could try connecting a powered hub to the second port to support the external drive.