primeval_god

The only thing you really need to change is your copy command. Instead of doing '/mnt/user/Downloads/@Converted' -> '/mnt/user/TV/xxx' do '/mnt/Storage/Downloads/@Converted' -> '/mnt/Cache/TV/xxx' copying from disk share to disk share. Just be sure not to do copies between disk shares and user shares.

This feature request is acknowledged though at this time I do not plan to implement it. I am trying to avoid reaching to deeply into dockerman for the implementation of this plugin. Sorry to disappoint.

The help icon switches the global help on in unraid. You should be able to turn it off by unclicking the help icon in the side bar.

Would you be able to run the following on the command line an PM the result to me? /usr/local/emhttp/plugins/compose.manager/scripts/compose.sh -c list

You do need to have the http:// portion of the address as well as the the IP and port numbers of your server. Also the [IP]:[PORT] syntax of dockerman will not work in the compose plugin.

If yours is the same post i saw on reddit it appears that you are trying to mount a device (disk drive) rather than a file. Unfortunately I have no experience with mounting devices rather than files.

Unfortunately I am unable to reproduce the issue on my local machine. It could be due to the docker folder plugin as i dont use it or test compatibility with it. There is also a chance it has something to do with unRAID 6.11.1 as I am still using 6.9.3 and dont directly test against newer versions. That said this is the first i report of the issue I have seen and I have no idea of what the distribution of unRAID versions this plugin is being run on. One other question, do you have any compose stacks running on your system that were not created through the compose plugin webui?

You must define containers in your compose yaml first. Once you do this the popup will show options for which labels can be modified. To my knowledge there is no plan to officially integrate compose support into unRAID. Dockerman is the official unRAID method of administering docker and is unlikely to go anywhere.

Would you be willing via PM to provide me with a list of Stack Names as well as the names of the project folders in which they reside (and any indirect paths that are used)?

This plugin does not provide such a thing. If you really want auto-updating for docker containers i would look into something like Watchtower.

Use the update stack button on the docker compose page. This is not normal. What OS version are you using? Is your plugin up to date? Do you have the docker folder plugin installed?

You forgot the repo name in your docker run command. nexius2/plex_user_manager:latest You have to use the whole thing.

No not at this time.

Yes there is. The plugin directory on the flash drive is meant to be managed only by the compose plugin and should contain only files create by the plugin. The option for the indirect path is meant to allow the user to build more complex stacks in their own directory while still integrating with the plugin. I would not recommend putting any extra files in the compose.manager folder.

I have absolutely no idea how the patches might interact with Docker Folder.

If the patch applied correctly, the patch button should disappear and on the docker containers page all of your stack containers (created with the compose plugin) should have "not available" in the version column.

The already reported issues are about unRAIDs builtin update check. I would suspect that the Fix Common Problem plugin piggybacks off of that but i dont know for sure.

But do you have the webUI patches enabled?

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.

@SCSI @Hendrik112 @elzik There is a new version that should fix the update function.

I would highly recommend running veracrypt as a docker container rather than trying to get a native package.

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.

@SCSI@Hendrik112 I am aware of this issue and working on a fix.

This thread really isnt the place to ask general questions about docker compose. Please try to keep things focused on the compose plugin itself.

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.