I’ve got a happy running system running 25.10.4 with one “custom” container for a Cisco WLC. I usually try all the betas and opted to try it as well since this hasn’t been a big deal. Unfortunately the TrueNAS SCALE 26.0.0-Beta 1 did not work and neither has TrueNAS SCALE 26.0.0-BETA.2. It is almost as though the data didn’t exist after booting the 26 system. I can reboot it into 26 and grab logs if that would be helpful, but the real questions are:
Is there a plan to support custom containers in 26?
Is the end goal to only support the pre-defined containers that show up in the beta?
Will the migration scripts get any different between now and GA in 26?
Should I just start fresh again on 26 and re-create the container storage ? (here we go again)
I have another VM on there of the WLC and it has never had these issues where TrueNAS changes the method of container deployment (truecharts/K8/incus) causes a server to not come up.
Why does that matter? The question isn’t about what I’m running or why I’m running it, the question is why doesn’t it work and what are the product end goals. Had I not been testing this, the feature may have failed to meet my needs later and I’d rather know now that I need to migrate so clearly I had a good idea to test this in beta.
Did you check for reported bugs or other forums posts about this issue?
You can get to the Jira bug system by clicking Report a Bug at the upper top right of the forum
Can you explain better what you mean by a “custom” or “pre-defined” container? As far as I know the expectation is that containers created in 25.10 should all migrate automatically.
Edit: Is the “custom” container possibly a legacy Incus VM that was created early on with the experimental feature and has be stuck on the Containers screen because you hadn’t migrated it back to Virtual Machines?
On a tangent note, where is the best place to follow the development/release/roadmap for 26 stable? I made the same mistake of setting up 26 BETA 2 thinking the release was just around the corner. Didn’t have any critical issues yet, but would help my anxiety to keep an eye on the dev diaries or something like that - if there are any.
I have to agree with @LarsR at this point as I expected the next Beta or RC to have been posted, already. There isn’t an expected schedule as this is the first change over to a ‘yearly’ release. I’m not sure if they had a lot more bugs in the Beta 2 than they thought or if they are aiming at a Release Candidate with a true Release to follow shortly.
I would strongly recommend going onto the General Availability trains unless you are in a position where you can be a Beta tester and submit feedback, without risking your data. I would expect any Beta or RC systems to second or third system that could be lost with no issue to the main data setups.
In 25.x this is what your new container workflow looks like. You are presented with something that looks quite a lot like how you build a VM in Vmware for instance. You are specifying cores/memory, then you can even specify the disks. This is the important part and major difference. In 25 you could pick a disk that is a dataset. So I created an essentially blank dataset for my app, then pointed to that and bob’s your uncle. In 26 it’s more like you only get the image browser which is similar to 25 if you browse for an existing linux variant or something that they have created I suppose is where these are coming from. Hence my crude use of “custom” container comment…unsure if that’s the accurate parlance to use here. The container in 26 when I was able to poke around before I realized my existing stuff was all broken was certainly different as you only get the browser and you aren’t specifying cores/disks/etc.
You can still attach storage to a container in 26, they’re just called Filesystem Devices and you add them after initially creating the container. You can also pin cores using Advanced Options > CPU Configuration on the Add Container screen. The UI might look different, but I don’t think there is actually any “custom” difference between your container and one that could be created in 26. The question is why did it fail to migrate?
I think you should probably file a bug report for this. I think you said you’d already reverted to 25.10.X, right? If so, I’d suggest first capturing a debug file on whatever version is currently running happily, then delete your current 26 boot environments and re-upgrade to BETA.2, capture an additional debug in BETA.2. Then you can use the smiley face icon to submit a bug report and attach both debug files.
Roger that. I do appreciate your response here and will do so and also thanks for the actual help here. It’s very hard to sort through what exactly is going to happen here and if I have to move a workload I’d much rather know now. So for that I’m very grateful.
