Containers under 26.0.0-Beta.1 seem unusable

TrueNAS General
1

Has anyone tried using the new non-experimental containers under 26.0.0-Beta.1

I thought I would give Debian (Something or other) &/or Ubuntu (Noble) a poke to see how things work out.

[Install Method:

  1. Set up bridge on new NIC

  2. Make sure settings are correct, default to bridge and correct pool

  3. Create new container, name and pick Ubuntu Noble

  4. Add NIC as despite it being default, its not selected

  5. Start Container

  6. Shell in

  7. Run IP A till IP address arrives

  8. ping ibm.com

    “ping: ibm.com: Temporary failure in name resolution”

I am find the following issues:

  1. The shell is almost unuseable. I can type a command, but cannot edit it. Also cursor up/down don’t work just producing the [ symbols
  2. The container eventually gets an IP address via the bridge & DHCP. But no DNS settings get to the container and whilst I am not an expert I cannot manage to set DNS. Thus almost nothing works. (APT to start with)

I am looking at replacing jailmaker - which just works on 25.x and at the moment am really hoping it works on 26

I am either doing something very basic wrong - or these LXC containers are badly fubar’d

I tried containers in 25.x as well. At least the networking works in them although there is a issue, something do do with runc and app armor in allthe ones I have tried (I maybe garbling that slightly)

2

That’s an issue with the incus version truenas uses and docker 29. Incus patched it days after that issue was discovered, but trurnas never updated incus past the affected version…

3

And I am not expecting them to fix something that they have abandoned.

But the current implementation in 26 is worse than 25. It appears to be broken

4

I really have to get around to setting up a 26 test sytsem… sadly i don’t have the time at the moment

Edit:
The only thing that comes to my mind with the dns issues you encountered would be a port conflict with port 53 so that resolved inside the lxc won’t start because port 53 is in use by another host process

5

Not to my knowledge. I don’t have any DNS services on any TrueNAS IP address. Everything is just a DNS Client.

6

Before you test DNS resolution, by using a FQDN:

Simply ping IP addresses:

Ping your own IP. Not really needed, unless “nothing works”, rule out things.

First, ping an internet IP, say 8.8.8.8. (If you get replies, your Default router/gateway is set correctly).
Then ping a FQDN (google.com), if it does not work, it’s your DNS setting.

If you can’t ping outside your network:
Ping your Default router/gateway (other ips in your local network if needed).

Check your Default router/gateway settings if pings reply.

7

I did actually test that - but as it worked I didn’t mention it.

Its definately the DNS settings, which should be handed out as part of the received DHCP address.

8

I just ran up a proxmox server. Created a container from what I think was the same LXC image. It just worked.

DNS, Apt etc all just worked. Even cursor command to edit / repeat CLI commands