Bastian

Greetings from 2026, thank you @wgstarks ! Your post helped me the most! For anyone finding this, also make sure to disable IP Address Assignment for the VLAN and set the Docker Custom Network Type to ipvlan.

A little bit of everything. NAS, Game Service, Docker Services, experimenting in Virtual Machines, Plex of course. With the electricity prices the uptime is getting kinda expensive, but I haven't found hardware with enough PCI lanes to replace my Threadripper

Hey Everyone, I am pretty new to the Plugin Development in Unraid and PHP in general. Currently I am trying to write a Disk Selector comparable to the Include/Exclude Disks in the Share Creation. What I have so far: DisplaySettings.page _(utilization indicator disks)_: : <select id="s1" name="usage_disks" multiple="multiple" style="display:none"> <?foreach ($disks as $disk):?> <?=mk_option_check(_var($var,'usage_disks'),_var($disk,'name'),_var($disk,'name'))?> <?endforeach;?> </select> Within the Page I can see that the selector gets correctly generated. But unlike the Share Creation Page, I am unable to create the span with the actual Selector Box. I can't find any hint within the Share Page where it is generated. Note: I am using mk_option_check on purpose, I don't want to limit it to diskN. The limitation to the correct disks will follow at a later point. Thank you very much in Advance!

A local pull-through cache could be used for Docker Images.

For better or worse, Lime Tech created their own Compose Notation to store the Run Configuration. Those are stored within /boot/config/plugins/dockerMan/templates-user. The way I would go with it (though never done it myself): Enable "Preserve Docker Networks" in the Docker Configuration in Unraid Create a new Docker Network using the CLI docker network create somedockernetwork Edit Swag and attach it to said network using the UI The network is available from the dropdown list in the UI Edit Swag and create the alias using the "Post Argument" (Advanced View) && docker network connect --alias cloud.domain.com --alias collabora.domain.com somedockernetwork swag

Unraids Web UI has no build in function do configure Docker Networks. Unraid automatically creates a new docker network for bonded interfaces and has the flag to preserve Docker Networks on restart (though it still can fail). If you need to add some additional network configuration, you will have to use the CLI. After the network is created, you can normally select in the Dropdown on editing the template. A lot of people edit the Template and add something along the line of && docker network blah for the Post Argument to have the configuration persistent.

That is hard to tell, as every container is written differently and has to be operated differently. If your docker image utilisation grows slowly, something has to write data to a non-mount-bind path. Here, you're part start: Collect data, a lot of it. I would start by cleaning the system, get it back to the origin state. Get a full report of the utilisation. Wait until it fills up again, make anther snapshot of the data. At this point you have two states you can compare against each other and draw conclusions. That done, you can start a more in-depth analysis. Why is that specific container filling up? I do not know if Docker has a build in function to list the Containers file-system by size, probably not. Check the known configuration for logs, temp data, etc. Check it against your container if it could be the case. At that point you also have something more specific you could ask the community. Based on the image you provided so far, your AI-Server takes most of the storage. Don't know the specific container, but it sounds like a candidate to eat through a lot of space.

The IP label can stay as it is. The label is only used by unraid for the Web UI Link in the Docker Tab. [IP] gets translated to the servers IP and the port gets translated to the external port from the mapping. It has no functionality for the container whatsoever. The docker run command compromises of docker run [options] image [command] [args]. command and args have to be in that order and command can't be omitted if you want to pass args. That is exactly what you are doing. You are passing the argument --with-database directly after the image, so it is a command. Since there is no executable called --with-database within the container, it fails. The maintainer already thought of that, as you can see in the template docker-compose file. Just fill the variable ADDITIONAL_PARAMETER with the parameters you want to set and remove them from the post arguments. Edit: The links on docker run aren't meant to be there, the forum auto. adds them oO

In the default configuration, the Docker Image is virtual storage storing all Images, Containers and Volumes. If a container is miss-configured or not really well written, it could happen that it write more data in than the virtual storage is able to store. In that case you get "No Space left on Device" exception. Or there are just too many running container, that could also happen. The first case can be check via the Container Size Button on the Docker Page. It lists all container by file system size. Someone else has to chime in, but I believe that excludes mount-bind paths. If all your containers are running, you could try a docker system prune -af --volumes. This deletes all unused volumes, pending images und stopped containers. Note: Run it at your own risk! To increase the size of the virtual disk, you have to stop your array, head over to Settings -> Docker and increase Docker vDisk size. This will delete all your Docker Data, so make sure everything important is (as it should be) mount-bind into the host system.

Sounds more like a configuration issue on your part. From that list I only know Plex and that should be able to survive a re-creation. Sometime the online service gets confused and you have to pin the libraries anew, but not the entire setup. Best to check your mount-bind against the official documentation. You can easily test it by just deleting the service. After creation from the template it should be like before.

The Docker Tab only shows Docker Containers. They are runtimes created from Docker Images. I don't want to exclude any fault on unraids part, but it can happen from time to time, that the Docker Daemon just can't start them. Nowadays less often, but you can still find bug reports about it. Happened with my Containers once or twice, with Docker Networks from time to time. Docker Containers aren't meant to be long-living or have sensitive data within their filesystem. They are meant to be able to be destroyed and re-created any time. That's why all the important stuff has to be mounted to the host filesystem. That's also why we have the templates. They store all the information on how the Container gets created. Keep your templates clean and tidy and you can recover such a case by just spinning all Containers back up again. A template is comparable to a runtime of an image (that's why you ca have multiple template for the same image, they just have to be named differently).

-v erzeugt automatisch den Ordner im Host-System, wenn er nicht bereits existiert. Woher weiß Docker, dass es ein Ordner und nicht eine Datei ist? Einfach, gar nicht. Docker erzeugt immer einen Ordner. Es hat also den Ordner /mnt/user/appdata/telegraf/telegraf.conf erzeugt und versucht ihn nun auf die Datei /etc/telegraf/telegraf.conf im Container zu binden. Daher auch die Fehlermeldung "Are you trying to mount a directory onto a file (or vice-versa)?". Lösche den Ordner im Host-System und passe den Pfad an, sodass er nur die Ordner und nicht die Datei beinhaltet. Die Datei kann nur eingebunden werden, wenn sie bereits zuvor im Host-System erstellt wurde.

I don't think that would be a feasible endeavour for two main reasons: Docker images aren't that static and an update, especially to latest, can often be missed Or the other way around, the maintainer pushes like crazy new images Project maintainer themself don't often publish changelogs themself. So more often than not, there is no way to make a list of changes We would end up with a database with a lot of holes, probably maintained by a few people for a handful of images. Without dis-validating your idea, the base of it is already flawed (sorry to say it that blunt ). In my opinion, Docker gave the false sense of security that any application can handle rolling updates. They can't. Especially databases, especially nextcloud, apparently also frigate. I can't really say "in the old days", I am not that old, but I know from my job to always use pinned versions. You never wan't to have any dependency or application change on its own without your influence or knowledge. Pin your application, watch the project on Github or whatever service they are using and backup -> update your application on a new release.

I would like to extend that to n tier, so everyone is satisfied. There shouldn't be much difference between two, three, four or even more tiers. I don't think it makes sense to run all the tiers in parallel, that isn't the intention of tiers, but to have them chained or run at different times. Three workflows I can think of The schedule of the mover hasn't been overwritten Run all the tiers in series The times have been overwritten (e.g. tier 2 daily (nvme -> ssd), tier 3 every week (ssd -> hdd)) Run them according to the cron jobs A mix of overwritten and default Group them according to their times and run serial inside the groups The most dangerous one, the user would have to make sure the groups don't overlap for best results That could be extended indefinitely.