Run `toolbox init-container` with a higher or a adjustable log level

[clement-dufour]

When a toolbox container is started e.g. on first use or after a host reboot, the container CMD instruction runs. This instruction is the toolbox init-container command. However, this command is always called with a log level of debug. This value looks hard coded (https://github.com/containers/toolbox/blob/main/src/cmd/create.go#L414). The log level used on toolbox creation with the --log-level flag has no effect.

This behavior bothers me because these logs are all registered as priority 3 (error) logs on the system journal as already discussed on another issue : #1381.

I would like this log level to be configurable or hard-coded to a higher level (such as error for example). It could follow the log level of the toolbox create invocation although this solution is not perfect.

I would be glad to provide more information on this or to submit a PR with a proposed solution.

[debarshiray]

When a toolbox container is started e.g. on first use or after a host reboot, the container CMD instruction runs. This instruction is the toolbox init-container command. However, this command is always called with a log level of debug. This value looks hard coded (https://github.com/containers/toolbox/blob/main/src/cmd/create.go#L414). The log level used on toolbox creation with the --log-level flag has no effect.

Yes, the entry point is hard coded as toolbox --log-level debug init-container because there's no way to change the metadata of a container, as known to Podman, after it has been created. So, if we want to change the log level later we will have to create some runtime mechanism to do it.

Maybe you already figured it out, but, just in case, Toolbx only uses one log level to keep things simple. So, there are only error and non-error messages meant for the user, and the debug logs.

The logs from toolbox init-container are connected to toolbox enter and run when they are run with the --verbose or --log-level debug flags.

This behavior bothers me because these logs are all registered as priority 3 (error) logs on the system journal as already discussed on another issue : #1381.

Are you bothered to see the debug logs show up in the systemd journal like in #1381 or is there another angle to this? I am wondering if this is duplicate of #1381