primeval_god

Yes I believe that the unRAID explicitly stops all containers before stopping the docker daemon.

It is not possible to upgrade the docker engine as a stand alone component. You will have to wait for the unraid os to catch up to the version you are looking for. In the interim you could spin up a VM or an LXC container and run a nested docker engine if you wanted to play around with those new features.

Its not clear to me exactly what you want to do. You can move the "projects" folder which is the location where the compose plugin creates and stores compose stacks. There is a setting for that path on the compose settings page, it will change the location but not move files you will have to manually copy the old projects folder to the new location. If you want to move individual stacks and you originally created your stacks using the "indirect" options such that the compose file is not stored in the projects folder than you can just move the folder containing a specific compose stack. To re-associate the stack with the compose plugin you would need to manually edit the path contained in the 'INDIRECT' file within the stack folder in the compose projects folder. An alternative to manually editing the INDIRECT file is to create a new indirect stack in the interface and copying your settings over from the old stack.

That is a feature request for unRAID/Dockerman. The compose plugin only controls the display of compose stacks, not individual containers.

Some containers that have an init system allow you to bind mount additional init scripts into the container that can hook into the up / down sequence. I have also seen setup that run "startup" scripts in a dedicated container that essentially runs the script then sleeps. They use a combination of health checks and container dependences to ensure other containers in the stack dont start until the scripts have finished.

At this time I consider such a feature out of the scope of this plugin. Have you considered using a tmpfs mount for your transcoding directory instead of a Ramdisk?

The file integrity plugin is supposed to watch the file file system for changes using inotify and automatically hash and rehash files when they are changed or moved (assuming that functionality is turned on). Unfortunately for large filesystems this uses a lot of inotify resources. You might check to make sure that your inotify watch limit hasnt been exceeded.

Use the docker cp command. https://docs.docker.com/reference/cli/docker/container/cp/

Off hand I am not certain. The autostart script triggers on the "STARTED" event, which is an unRAID system event that plugins can hook scripts into. I can never remember where the documentation for those events is. No. Dockerman autostart and Compose autostart are completely separate. If you have dependencies between containers there are some ways to handle them with docker health checks but in general containers that have dependencies should all be part of the same manager and stack. I would guess this is because of some dependency between containers that causes the container to fail on initial startup. With restart: always it will continually try and restart after failure until its dependency is ready.

The checks for broken templates are automated.

@Mainfrezzer Remind me again where we can find that above bit of information about broken templates. I always forget that there is an accessible way to see template errors.

Since your repo was previously available you will want to send a PM to @Squid with questions.

Is it all containers or just specific ones? What kind of network are the containers attached to (host, bridge, macvlan, ipvlan, other)? What does the webui field in the container template look like? Possibly, if it ends up being problem with the Folderview2 plugin you would need to ask in that plugins support forum.

Interesting, are you able to manually pull the images with just docker?

There is a PR open that would allow this, however I have not had time to evaluate it as of yet. That said this plugin is not designed to manage arbitrary compose stacks, it is designed to manage the simple stacks created via its gui, which always use the same file name.

The trick would be either getting a container with with both python and ffmpeg installed.

Along these lines, my suggestion would be to reorganize the "Stable Releases" and "Prereleases" categories in the "Bug Reports" so that one category houses all bug reports (since we already put the version number in the bug title and bugs may span several releases) and use the other category purely for the pre-release announcement and discussion threads. I would also be nice if there were a convenient way to tag each issue with all the releases it has been confirmed on.

https://forums.unraid.net/forum/53-feature-requests/ So far as i know the feature request subforum is still the place to make requests. Always try searching for existing requests before posting.

I am not exactly sure what you are asking. That said I dont have any more idea than you of what changes Limetech is planning for unRAID. I am just a community member not affiliated with Limetech.

net.unraid.docker.icon: 'https://github.com/0neTX/UnRAID_Template/blob/main/bw-export/icon.png?raw=true' net.unraid.docker.webui: '' net.unraid.docker.shell: 'sh'UNRAID supports these labels as hints to the UI as to what to display. All the compose plugin does is provide a UI to allow you to set these labels for the containers in your compose stack the unRAID web ui handles the rest. To my knowledge (I am not running the latest unraid version) unraid still has an issue with its icon caching where changing the icon url set by a label wont actually change the displayed icon short of manually deleting the cached icons (and if i remember correctly no icon still counts as an icon). I believe there is discussion about this issue and how to delete the icon cache somewhere farther back in this thread.

Add another WORKDIR line at the end of the dockerfile. Or use the --workdir option in your run command

I am not sure you need to modify the image at all. I think you could just change the docker run command. Change the CMD portion of the docker run command to something like sleep infinity and change the -it flag to -d to run the container in detached mode.

Is there something in particular i have to do to get a linux machine to correctly move deleted files into the .Recycle.Bin folder instead of creating its own .trash-1000 folder? I have previously only accessed shares via a windows machine.

https://forums.unraid.net/bug-reports/

Never tried such a thing but this is not a function of the compose plugin ui. The snippet you show above is the Dockerman ui which is built into unraid.