Yes, sir DragonFish I uploaded details of the last time it occurred here. Active Directory corruption
Pretty much the only difference I noticed this time is it recurred after stripping ACLs and reapplying on the next day, and did not reoccur after clearing the AD cache but I have no real evidence that is related for sure.
I am going to test Electric Eel on my home setup but that is pretty much just Truenas SMB + Emby without AD.
I suggest checking out the info shared on the post call for testing
Custom apps will be supported and custom app migration is planned for RC.1, more details to follow.
Is it expected that we will have to reconfigure existing apps like Emby?
In my initial testing after rebooting my Emby installation was gone, I could reinstall it but that would require setting it all back up again from scratch. It appears apps like Emby are considered Truenas apps not custom ones. But I may be missunderstanding.
Also I have a WX3100 in my NAS so I will be sure to test AMD GPU passthrough.
This link shows that it will not currently migrate: GitHub - truenas/apps
It would be very helpful if there was a way to kick file access for SMB sessions per file (semi frequently have users open files and walk away), windows/office seems to hand out write locks like candy.
Modular NVIDIA Drivers: The binary drivers for NVIDIA GPUs are now decoupled from the TrueNAS installation, allowing for these drivers to be updated on separate cycles from the main product.
I am trying out electric eel and noticed I no longer can pass nvidia gpus through to apps. Is it related to this? How do we go about install these drivers?
Suggest you start a new thread on thisā¦ if no answers, then it becomes a Feature Request.
Take a look in the release notes info on the Nvidia drives is included.
Hey, thanks for the reply. That did the trick. Thought I read the right docs, but I must have skipped over that part.
Iām a little curious as to how the TrueNAS team looks at Docker and Podman and chooses between them.
As am I.
Well, most software comes packaged for Docker and often specifically use docker-compose. So you need to be able reliably support docker-compose.
Podman is trying with its podman compose command but its not 100% drop-in replacement.
From what I read Podman in-house tool similar to Docker Compose is called Podman Quadlets.
So if you try using podman compose for docker compose files you are asking for trouble.
iX needs for the packages to just reliably work. And authors of those packages are testing it for Docker, not Podman. So while both of those solutions are capable of running OCI containers itās very much safer choice to just use Docker.
Thanks for providing an excellent answer.
I did a fresh install on two different systems (both VMs), and set up a pool so I could check out how the apps work. But on both systems, I get a Kubernetes error:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/middlewared/utils/service/call.py", line 25, in _method_lookup
serviceobj = self.get_service(service)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/utils/plugins.py", line 144, in get_service
return self._services_aliases[name]
~~~~~~~~~~~~~~~~~~~~~~^^^^^^
KeyError: 'kubernetes'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/middlewared/main.py", line 357, in on_message
serviceobj, methodobj = self.middleware._method_lookup(message['method'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/utils/service/call.py", line 27, in _method_lookup
raise CallError(f'Service {service!r} not found', CallError.ENOMETHOD)
middlewared.service_exception.CallError: [ENOMETHOD] Service 'kubernetes' not found
Based on the release notes, I didnāt see anything about the apps not working.
@Travis Can you share some more details on where this error was seen? Did you deploy the 24.10-BETA.1 or a nightly package?
@ABain It is this image: TrueNAS-SCALE-24.10.0-MASTER-20240716-035108.iso ā¦ which looks like the nightly. Iāll try the actual beta.
I have attached two images of the error when I go to āAppsā.
@Travis yes please try the BETA that nightly you have is nearly 6 weeks old
Thatās an ancient nightly from July 16.
Perhaps caused because of this issue:
https://ixsystems.atlassian.net/issues/NAS-129765
Because obviously 0716 is the newest build
Anyway, use the beta, or if you must, then a nightly which is only a few days old, not months 
