Init/Shutdown Scripts - Difference between a "command" and "script"

TrueNAS General
1

I have a script that start and stop my containers via the
“System → Advanced → Init/Shutdown Scripts” GUI.

No issues with starting them as a “Pre Init” command → “containers --startall”
But will not accept → “containers --startall” as a script.

When shutting them down, the command → “containers --stopall” does not seem to do anything, and I cannot find the relevant logs to investigate.

The “Timeout” for the shutdown is set to 300 seconds.

Also the “Type” as a script does not work either.

The scripts themselves work without issues via the command line.

Any suggestions will be appreciated.

Thanks

2

If yhe scripts run from the command line then try to do this… cd into the directory where the script recides then exucute like this…
cd /mnt/pool/scripts && ./myscriptname.sh

There was security hardenning which makes it a bit more involved to run a script via cron and I suspect what you are doing.

3

I shall give that a try.

Thanks…

4

So I gave it a try, and still did not work.
I thought to keep it simple, and just did the following:

echo “Testing The Shutdown Script” >/var/log/messages

That works no problem, whether it’s a command or added to a script.

Pondering, I realised the reason my containers are not stopping gracefully is because during the shutdown process, docker is no longer available, and hence my commands are not taking affect.

So my question now is, how to gracefully shutdown containers prior to shutting down without having to manually run the scripts…

5

Doesn’t TrueNAS shut down all apps on system shutdown? :thinking:

1 Like
6

Exactly. The default shutdown process likely handles everything gracefully.

Apps, VMs, mounts, locking encrypted datasets, etc. I would never suspect it would act otherwise.

7

If I don’t restart them on startup, the STATUS of “docker ps -a” is showing as Exited, and not Stopped, which to me sounds as though they have just had their legs chopped off.

8

Are these apps installed via the UI or docker commands in shell?

9

They are installed via the GUI - Applications → Discover Apps → Custom App → Install via YAML…

10

Custom apps? I yes, what is the restart policy set to?

11

They are set to → “restart: on-failure”.
I have no issues in restarting them, its when the system is rebooted, updated or shutdown that they do not seem to shutdown gracefully.

Perhaps I should just stop them manually via the GUI “select all” function.

12

I’d recommend “restart unless stopped” or similar (from memory).

1 Like
13

I will try that one out.

Thanks…

14

So setting the restart policy to “unless stopped” confirms that the container status is definitely in the “Exited” state, and not stopped as they all restarted by themselves when the docker daemon restarted.

I migrated my containers from CentOS thinking I could kill two birds with one stone, but the fact that the data and databases could get corrupted is not a nice way forward.
I will review the situation, and hopefully come up with a solution, or perhaps revert to using Rocky as a replacement for CentOS, but it means having two servers.

Anyway thanks for all your help.