primeval_god

At this time I have no plans to support such a thing. Some of the core features of the plugin are currently based on the folder structure it creates in the plugin config directory on the flash drive.

I dont use vlans myself so i could be wrong, but i dont believe that real networks are by default available as interfaces for a docker container. I think you would need to use the docker network create command to create a custom macvlan network that is attached to br0.10 for your containers to connect to.

Actually such a network configuration is very common when it comes to microservice containers. The reason it may not seem to be as common with docker is that much of the containerization community has "moved on" from docker when it comes to managing multicontainer apps to more feature rich container orchestration tools like kubernetes (note moved on is a bit over the top as docker still underpins many of the orchestrators). So to the heart the issue, the unRAID platform integrated docker as a means to gain easily installable and sandboxed applications. The unRAID webui is focused primarily on supporting single container applications. Thusly there has been little need to support more complex networking schemes in the interface. That said, under the hood it is just docker and additional networks can be attached to a docker container with the docker cli. If you are determined to step beyond unRAIDs single container paradigm i suggest looking into the docker compose plugin for unRAID (full disclosure I maintain it).

No they must be reinstalled on bootup.

New update is out today. It adds a better editor for compose files and a button to get the logs for a compose stack. Note that the logs button only functions in "Experimental" mode which can be activated from the settings menu.

Yes. The plan is eventually to add a helper to make adding the correct labels a one click.

Fixed in the latest release. Good idea i will look into it.

Pretty sure you just uninstall it from the plugins page and then restart your server like any other plugin. I dont think the uninstall process removes hashes from already hashed files though. And the logs are probably not removed either. Any chance those are just leftover from the last time you had it installed?

In docker terminology registry and image name are not really separate. Just put whatever image name you use in your docker run statement into the repository field and it should work. If you look at the output of 'docker images' in the console you will see that column for the image name is the repository column.

Isnt the issue that for something like this to work unRAID's nginx instance would have to be exposed to the internet, which is something you should never do.

@bonienl Does the 6.10 implementation of this feature cache the icons (specified by label) on disk like it does with icons specified in templates?

The requirements for putting a swapfile on a btrfs filesystem are a bit tricky. The plugin does its best to automate it but here are a few gotchas, the steps you list below would not work on a BTRFS filesystem. On BTRFS the swapfile must be created in BTRFS subvolume with COW disabled. This is basically what the plugin does, swapon is does at the "started" event and swapoff at "stopping_svcs". Even with a manually created swapfile you should be able to point the plugin config at the file and have it manage it. Otherwise the user scripts plugin is a good way to run scripts on startup and shutdown. There are other ways which might get you closer to startup but i dont know enough about them to recommend them. Search the forum for adding commands to the go file. Just speaking in general though swap is typically not considered as a replacement for having enough ram. This is especially true for unRAID where the OS loads into an runs completely from RAM.

https://raw.githubusercontent.com/dcflachs/swapfile_plugin/master/swapfile.plg

The primary purpose of this plugin is to provide a convenient way to install docker compose on unRAID. With this plugin installed docker compose is available through the command line. The ability to create and manage compose stacks via the web ui is still very much a work in progress. As it is stands the plugin gui will not display or manage arbitrary compose stacks running on unRAID, only those that are created with the plugin gui itself. Additionally the currently implemented features are mostly about control of the stack, there is not really anything displayed about the status of running stacks yet.

Try changing the version of your compose file from 3 to 3.3. Also just a point of order these are not volumes per se, they are bind mounts to folders. I dont think the -V option for up and down are necessary when talking about bind mounts.

Correct those are the actual short syntax volume mount lines.

This question probably belongs in the thread about this guide in the guide section of the forum. That said I think the solution should be easy enough. I believe you just need to edit your compose.yml file and add the slave option to the end of your volume mount lines. :rw,slave or :ro,slave If the compose file is using the long syntax for the mounts rather than the short then things are a bit different. Either way a reference to the mount syntax is here https://docs.docker.com/compose/compose-file/compose-file-v3/#volumes

If you installed the compose plugin you should use docker compose not docker-compose. The older docker-compose syntax should still work i believe but the version of compose installed by the plugin makes compose a subcommand of the docker cli.

Yes thats already in the works.

For instance consider a subvolume at /mnt/cache/Video_Conversion/test/sv trying to create a snapshot and place it in the non-existing folder /mnt/cache/Video_Conversion/test/snaps fails.

Very similar I use Opera normally and Firefox for unRAID and most of my internal sites.

First off awesome work! Glad to see someone tackling this as a plugin. I have been playing around with it a bit and i have run into a few oddities. Every Snapshot or Send action i take from the GUI returns a popup that says "Fail" even when the action obviously succeeds (snapshot is created and page updates to show the new snapshot). Also it seems that the plugin seems to choke when the destination directory is a tree of non existing directories (I would expect it to create the directories). Finally a point of order, despite the currently conversation being in this thread doesnt conversation about your plugin belong under its support thread rather than in the feature requests subforum?

This is a fairly minor annoyance to me but often I visit the forum and see unread posts in the Announcements sub and think 'oh something new!' only to find that its someone responding to an old release announcement. I kind of wish that the Announcements sub was only updated when limetech had something new to announce. Maybe we could have an "Announcements Discussions" sub and every announcement would get an official locked post in Announcements with a link to a discussion thread in Announcements Discussions (discussion thread would link back to announcement of course)?