I vaguely remember docker compose is coming to TrueNAS SCALE. What's the rough timeline for that?

I have a TrueNAS CORE installation and will need to migrate to SCALE, however doing so during the transition period from Kubernetes to Docker Compose it’s useless.

I remember reading the next version of SCALE will use Docker Compose. Is this correct?
What’s a rough timeline for when the docker compose version will come out?

Should I upgrade CORE to 13.3 (from 13.0) or is the SCALE update coming soon enough that I can skip it?

The beta version for Electric Eel should be around soometime in August.

Thank you, this is great.

I also found: 24.10 (Electric Eel) Development Notes | TrueNAS Documentation Hub

Which says the stable release will be roughly at the end of October. I’ll prepare for that time

FYI, the 24 in 24.10 is the year, and, the 10 is the month.

2 Likes

One other point, the “first” release of any software tends to be less complete or include bugs. (Programming is the process of installing bugs :slight_smile: and debugging is the process of making programs work.)

So, if someone wanted a guaranteed functional Docker, then waiting for the version AFTER Electric Eel would be best. (Thus, not version 1 of the new feature.)

1 Like

Fair point, but docker-compose is not a newly developped software, merely a new inclusion in Electric Eel, so I’d expect that it works fine in .1 or .2 of Electric Eel itself, only allowing for some teething issues.

Yeah, docker compose quite polished. But, the UI that configures it may not be. Or, networking. However, if we can also manually maintain the yaml then less likely to have bad stuff. Docker by itself I don’t think is the issue, it’s other stuff, newer zfs version, newer kernel, etc. where the bugs can come in. I never load the .0 anyway so still won’t.

That is a valid statement,so i might wait.
CORE has a bug that won’t be fixed which causes vms with multiple cores to reach some sort of deadlock status where the only solution is hard rebooting the vm.

It is fixed in the next version of freebsd, but we won’t be getting that one, so I’m already in a buggy situation, hence I’m evaluating

This was the motivating factor for my scale migration.

Being able to use Sandboxes was then a secondary reason and meant I no longer needed the VM anyway.

I agree.
What do you mean by sandboxes? I was reading there is jailmaker, then there are VMs, apps and docker compose will be usable in some way that I don’t understand yet.

I’m very familiar with writing compose files (at work I do that a lot), so I was hoping to be able to do that, although “apps” might cover all my home needs with no additional effort.

I have as video which covers sandboxes fairly well.

In Electric Eel you won’t need the sandbox to run docker (and compose). Additionally the apps will be made using compose too.

And dockge is installable as an app.

I cover this in a different video

2 Likes

Amazing, that means I can get native performance and easy mounting by just using dockerge as an app and running a bunch of compose, or just multiple apps (if my usecases are present).

Do you know if it’s possible to use different image providers, or just docker hub?

Just specify the registry in the image path.

ie for Linux Server’s Heimdall image

services:
  heimdall:
    image: lscr.io/linuxserver/heimdall:latest    <------
    container_name: heimdall
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - /path/to/heimdall/config:/config
    ports:
      - 80:80
      - 443:443
    restart: unless-stopped

Yes but how would I provide authentication? Is there a json file I can edit like in the docker system service on debian?

When using the Debian sandbox it is exactly the same as a Debian docker install.

Edit the daemon.json file

1 Like