This is it:
jamcom2@jamcom2:~$ ls -la /
total 3063904
drwxr-xr-x 22 root root 4096 Mar 28 18:12 .
drwxr-xr-x 22 root root 4096 Mar 28 18:12 ..
drwxr-xr-x 2 root root 4096 Mar 28 18:12 .cache
drwxrwxrwx 5 root root 4096 Apr 15 12:33 JamCom2files
lrwxrwxrwx 1 root root 7 Feb 1 18:20 bin -> usr/bin
drwxr-xr-x 3 root root 4096 Apr 15 12:17 boot
drwxr-xr-x 2 root root 4096 Mar 6 14:37 cdrom
drwxr-xr-x 21 root root 4640 Apr 15 19:33 dev
drwxr-xr-x 144 root root 12288 Apr 14 11:44 etc
drwxr-xr-x 3 root root 4096 Mar 6 14:57 home
lrwxrwxrwx 1 root root 7 Feb 1 18:20 lib -> usr/lib
lrwxrwxrwx 1 root root 9 Feb 1 18:20 lib32 -> usr/lib32
lrwxrwxrwx 1 root root 9 Feb 1 18:20 lib64 -> usr/lib64
lrwxrwxrwx 1 root root 10 Feb 1 18:20 libx32 -> usr/libx32
drwx------ 2 root root 16384 Mar 6 14:35 lost+found
drwxr-xr-x 3 root root 4096 Mar 7 15:00 media
drwxr-xr-x 4 root root 4096 Apr 4 12:12 mnt
drwxr-xr-x 3 root root 4096 Mar 28 13:01 opt
dr-xr-xr-x 242 root root 0 Apr 15 19:31 proc
drwx------ 7 root root 4096 Apr 4 12:18 root
drwxr-xr-x 36 root root 1100 Apr 15 19:33 run
lrwxrwxrwx 1 root root 8 Feb 1 18:20 sbin -> usr/sbin
drwxr-xr-x 8 root root 4096 Mar 6 14:59 snap
drwxr-xr-x 2 root root 4096 Feb 1 18:20 srv
-rw------- 1 root root 3137339392 Mar 6 14:40 swap.img
dr-xr-xr-x 13 root root 0 Apr 15 19:31 sys
drwxrwxrwt 21 root root 4096 Apr 15 21:12 tmp
drwxr-xr-x 15 root root 4096 Apr 14 11:44 usr
drwxr-xr-x 14 root root 4096 Mar 7 14:32 var
jamcom2@jamcom2:~$
Apparently everything is owned by root, but I can write and read no problem, and also why docker runs with sudo just in case.