docker/helm/kubectl commands in shell

[wfg]

I'm excited to see Linux-based TrueNAS shipping with Docker and Kubernetes!

I've been testing out the apps through the UI and began trying to convert my Docker Compose files to Helm then massaging those into TrueNAS-compatible charts. It's not impossible, but if I could cut out the last step, it'd save a lot of headache. I know it's possible to run docker/helm/kubectl manually, but is it going to be "supported" in TrueNAS SCALE, or are the UI apps going to be the only way to run container workloads?

 

[overeat]

Some info on kubectl and ports below 9000 with TrueNas SCALE

Docker-within-Scale Questions

I'm trying to get as far as I can troubleshooting and learning about docker use from those platforms documentation. But, I'm a bit stuck due to not knowing how it is implemented within Scale. For example, many available documents refer to using "kubectl" commands. But, within Scale, the command...

www.truenas.com

I was able to Sidebar -> Apps -> Launch Docker Image and then see my docker image as an "installed app"

There's some issues with ports/port mapping below 9000 which is mentioned in thread I posted above.

Hope this helps someone.

 

[overeat]

Also here's some useful kubectl commands for newbs

How to run a Docker container on SCALE for dummies?

Hi all, is there a write up already on how to do this? No large orchestration (k8s) needed. What would I have to do given a docker-compose.yml to run it on SCALE in a way that will keep the settings across updates and restart the container on reboot? Not familiar with that "helm" thing, either...

www.truenas.com

 

[brando56894]

Traditionally IX Systems wants you to do everything via the GUI as the middleware does a lot of stuff that is bypassed if you go straight to the CLI, so most likely doing stuff outside of the GUI will always be unsupported, except for features in progress of course.

 

[inman.turbo]

The middleware is essentially an event-sourced python app. It saves all of your actions in the GUI as events in an SQLite 'config' database. Then if you need to upgrade, switch trains, restore or migrate your system, it will replay all of your events to achieve the desired state.

If you bypass the GUI (and/or CLI) your actions will not be recorded, and the state of any new/restored (or possibly even just updated) system will not reflect any of your actions completed outside of the GUI (and/or CLI).

By CLI I mean the interactive TrueNas command line client. Not your standard system shell.

I should mention that it is not the GUI itself that does all of this, but the HTTP API that it sends it's requests through. This means that it is also possible to create your own clients, CLI or GUI, using the same API.