wicket: /tmp/wicket.log has wrong owner (chown) after running wicket as root from within the switch zone

I tried to ssh into wicket from the outside, and I got:

Error: error opening log file /tmp/wicket.log

Caused by:
    Permission denied (os error 13)

This was due to:

root@oxz_switch1:~# ls -la /tmp/wicket.log 
-rw-r--r--   1 root     root       40391 Mar  7 22:36 /tmp/wicket.log

This fixed the issue:

root@oxz_switch1:~# chown wicket:wicket /tmp/wicket.log 
root@oxz_switch1:~# ls -la /tmp/wicket.log 
-rw-r--r--   1 wicket   wicket     40391 Mar  7 22:36 /tmp/wicket.log

The owner of /tmp/wicket.log can be root under the following circumstances, where /tmp/wicket.log is not present before running wicket:

root@oxz_switch0:~# rm /tmp/wicket.log
root@oxz_switch0:~# /opt/oxide/wicket/bin/wicket
root@oxz_switch0:~# ls -la /tmp/wicket.log 
-rw-r--r--   1 root     root     1719133 Mar  9 19:19 /tmp/wicket.log

@jgallagher writes, regarding running wicket as root from within the switch zone:

it could either chown the file itself (if running as root), or not fail on launch if the log file isn't writeable (if not), or both

Start with the /opt/oxide/wicket/bin/wicket entry point and reproduce launching it as root when /tmp/wicket.log is absent. Inspect how the log file is created and how launch handles an unwritable log; done means the resulting log can be opened by wicket from outside the switch zone, with the chosen behavior for non-writable logs covered.