SCALE works with Helm and k8s, which doesn't really work with container settings. It's all a bit abstracted away, even ignoring the abstraction of the GUI.
Jails vs k8s, is a world of difference... I think it's best not to talk too much about how things from a jail can be done in k8s. Because it's like explaining totally different solutions to a problem.
True. But when it comes to service as I described, it's as simple that it shouldn't be problem to either. Solution with jail CAN be solution with image, but I'd rather make it different this time.
Spinning up containers when printers come and go, seems like a bad idea... prone to failure and totally not needed, as USB already has hotplug which just about every decent print server should be able to deal with afaik.
Forget the start-stop script to begin with.
You need to set the "securityContext.privileged", to "True" and create a hostPath mount to the "/dev/" usb device references. There are some examples on how to do it in the TrueCharts repository. (if you have a good reference for a print server, i'm open for suggestions there too)
See:
https://github.com/truecharts/truecharts
Besides securityContext.Privilaged, everything else (hostPath mounts) is already available in the GUI.
Containers? can you please use correct k8s terminology...
Use Helm directly, like everyone else
It looks like you think the new apps/containers are somewhat similair to standard docker or jails. It's not. Its Helm-Kubernetes based. On linux, so forget about all the jail steps needed to connect devices to jails. It's so much different that I doubt it's going to help you to know how to do that.
Missed those examples. Sorry. I am using cups with Samsung
driver and avahi to advertise AirPrint.
This means that cups and avahi services need to stop when printer is off-line and come back up when printer is up.
Sorry for incorrect terminology, it's just that I've built my own with Dockerfile, and have used to call it container. Even though it uses kubernetes or whatever available, result is same, it runs my custom combination of applications and scripts.
Well there is some similarity, but I wouldn't say jails are the same thing. Actually I would had loved to go with TrueNAS CORE, but I decided to give scale a try just for.. Well, accordingly to GUI, docker images :)
Why? Because I might be wrong here, but due to that they take a lot less space, I think they are more light-weight than jails in BSD (not forgetting difference..) and for that, I'd like to think that they consume less resources. I am a fan of alpine based... Images. And minimal images when ever possible.
Explanation about jail version of this was just
how I archieved this with CORE. Maybe I should had gone the simpler way and just tell that I need to provide direct access to device nodes from my container and receive notifications from udev, without explaining further why I need this.
For the moment, I haven't yet created my own repository with helm charts, will be looking to that when I have a image that does what I want, since it's not necessary until base image has necessary functionality. Sure, with charts I can customise installation of image, for example, set admin password for printer's server or something like that if I want, but I am not really attempting to create a public repository competing with existing ones, I just have my own requirements and rather roll my own here; I'll check later, but probably with this, I can create my image as planned.
You seem eager to participation. You are welcome :)
My plans actually consist of running 2 apps in my setup, GitLab and this printer server. Hopefully GitLab will eventually find it's way to truecharts, but more likely I still want to go with minimalism and go with Alpine based setup with that too.
Since you seem to have a lot of expertise with images, could you explain to me why most images are based on bigger base images like for example, ubuntu? I see the point when you want to provide a service that needs more components that are not available in the smaller distribution, but for example, exim4 server, or caching server, wouldn't it be better to go with minimal setup instead of larger distribution that comes with more than necessary? I like images for their fast deployment, small size, simplicity (when image is just running one service for example) and independence from other components in system, but some of this goes away when using bigger distribution. So far all my requirements can be done with smaller distributions, even my web server (not running locally and base os is CentOS) runs all it's services visible from internet with Podman containers.
