After update from 25 early adopter to 26 early adopter, docker failing to start on boot (Unable to determine default interface)

I checked this morning and see that 26 was available to the early adopter channel so I went for it.

First thing I notice is that the Apps are failing with the message:
Failed to configure docker for Applications: Unable to determine default interface

If I unset the pool and reset it then it works but all my apps are missing.

And, the fix does not survive a reboot.

Any suggestions?

I have two interfaces with the slower interface being for admin general purpose and is set to a bridge mode.

Unless you want to stay a BETA tester and use Report a Bug at the top of the forums, I would suggest changing back to 25.10 series and removing the 26 Beta boot environment. You can do a manual update with 25.10.3 (EA status) if you wish. If you want a GA status, you would have to roll back to 25.10 or 25.10.1 and change the train status to GA and then remove the later boot environments.

Thank you, I will use the report a bug instead of posting. Not sure if it is a bug or user error. Learning the process…

Feel free to post. It’s more likely to be a Bug because that’s the 26 Beta. It’s best if items get caught early, if that is.

I reverted back to 25.10 and the Apps are working again. I’ll report the issue to the bug list as my experience. Could still be user error.

Same here. Filed a report

Were you on 26 Beta or a different version of 26? Ticket is showing TrueNAS Nightlies.
https://ixsystems.atlassian.net/browse/NAS-140690

26.04.0-MASTER-20260224-092256

Not sure how to select beta. It has popped up one time in suggest, then gone. The only way to update to 26 was to select “developer” and now I’m stick with it

Not seeing 26.0.0-BETA.1 from 25.10.3 was a temporary glitch. On the Early Adopter train, 26.0.0-BETA.1 is now available.

Go back to 25.10.3, then delete the boot entry for 26 nightly, and update again to 26.0.0-BETA.1, on Early Adopter train. Don’t use Developer train.

I just tried the updated again from 25.10.3 using the early adopter channel to 26.0.0.BETA1 and it failed the same way on the App Start. I have two debug files (one from 25.10.3 and the other from 26) that I can send someone but I don’t want to post them due to the warning about sensitive data.

The UI has a file a bug option that should attach a debug in such a way that it can’t be seen by just anyone, only by ix

Is that for just paid customers?

No, that’s in CE, available for free. Send Feedback Smiley Face (ideally from the place in the UI where you have trouble), click on the “Report a bug” tab, enter a Subject and Message, log into Jira when it prompts you. It defaults to attaching a debug report and a screenshot.

1 Like

You should be able to log into your JIRA ticket after it was created and add the debug. You should have received an email from the JIRA system with a link, also. If that doesn’t work, DM a TrueNAS employee from the USERS listing on the forums, like @HoneyBadger

Simple downgrade to 26.0.0.BETA1 was not enough. Setting static IP on br1 - that’s what resolved the problem with apps.

So, did I get it right, that there’s no option to use DHCP on bridge iface?

FWIW: in my case, simply removing the IPv6 entry from Apps / Configuration / Settings / Address Pools was enough to clear the “determine default interface” blockage and resume apps service.

1 Like

FWIW #2: this same change just resolved the same symptom on a second system on the same LAN. (This second system experimental and neglected; still running 26.0.0-MASTER+20260324-020147 for the past 25 days.)