Fatdog64 runs as root - but podman will not!

[DevilDogLinux]

Issue Description

Hi - very new to podman this will be a problem on my end.

Obtained a podman binary...
https://github.com/mgoltzsche/podman-static/releases/latest/download/podman-linux-amd64.tar.gz

rt-click installed it.

# podman --version
WARN[0000] The storage 'driver' option should be set in /root/.config/containers/storage.conf. A driver was picked automatically. 
podman version 4.6.1

# podman machine init
WARN[0000] The storage 'driver' option should be set in /root/.config/containers/storage.conf. A driver was picked automatically. 
Error: cannot run command "podman machine init" as root


Having created a podman user...

# su podman
podman$ podman machine init --disk-size 2
ERRO[0000] XDG_RUNTIME_DIR directory "/tmp/runtime-root" is not owned by the current user 

Fix ^^ that perms problem, another and another pop up. To the point that I am fairly sure I've got something badly wrong.

eg...

podman$ podman info
ERRO[0000] stat /root/.config/containers/storage.conf: permission denied 
podman$ 

Ideas welcome!

FD64 runs as root - would like podman to do the same!

Steps to reproduce the issue

Steps to reproduce the issue

1. On FD64-813 pull any podman binary release.
2. RtClick Install

Describe the results you received

podman refuses to run as root

create a podman user ... that user cannot access /root/.config/...

Describe the results you expected

Expected podman to run as root from a root terminal.

podman info output

podman version 4.6.1
Fatdog64-813
uname -a
Linux host 5.19.14 #1 SMP PREEMPT_DYNAMIC Thu Oct 6 02:08:05 AEST 2022 x86_64 AMD Athlon(tm) II X2 215 Processor AuthenticAMD GNU/Linux

Podman info:
# podman info
WARN[0000] The storage 'driver' option should be set in /root/.config/containers/storage.conf. A driver was picked automatically. 
host:
  arch: amd64
  buildahVersion: 1.31.2
  cgroupControllers: []
  cgroupManager: cgroupfs
  cgroupVersion: v1
  conmon:
    package: Unknown
    path: /usr/local/lib/podman/conmon
    version: 'conmon version 2.1.7, commit: f633919178f6c8ee4fb41b848a056ec33f8d707d'
  cpuUtilization:
    idlePercent: 50.49
    systemPercent: 6.2
    userPercent: 43.31
  cpus: 2
  databaseBackend: boltdb
  distribution:
    distribution: '"fatdog64"'
    version: "813"
  eventLogger: file
  freeLocks: 2048
  hostname: host
  idMappings:
    gidmap: null
    uidmap: null
  kernel: 5.19.14
  linkmode: dynamic
  logDriver: k8s-file
  memFree: 429522944
  memTotal: 12030590976
  networkBackend: cni
  networkBackendInfo:
    backend: cni
    dns: {}
  ociRuntime:
    name: runc
    package: Unknown
    path: /usr/local/bin/runc
    version: |-
      runc version 1.1.7
      commit: v1.1.7-0-g860f061
      spec: 1.0.2-dev
      go: go1.18.10
      libseccomp: 2.5.4
  os: linux
  pasta:
    executable: ""
    package: ""
    version: ""
  remoteSocket:
    path: /run/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: false
    seccompEnabled: true
    seccompProfilePath: ""
    selinuxEnabled: false
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/local/bin/slirp4netns
    package: Unknown
    version: |-
      slirp4netns version 1.2.0
      commit: 656041d45cfca7a4176f6b7eed9e4fe6c11e8383
      libslirp: 4.7.0
      SLIRP_CONFIG_VERSION_MAX: 4
      libseccomp: 2.5.4
  swapFree: 11989032960
  swapTotal: 17179865088
  uptime: 42h 3m 21.00s (Approximately 1.75 days)
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  network:
  - bridge
  - macvlan
  - ipvlan
  volume:
  - local
registries:
  search:
  - docker.io
  - registry.fedoraproject.org
  - registry.access.redhat.com
store:
  configFile: /root/.config/containers/storage.conf
  containerStore:
    number: 0
    paused: 0
    running: 0
    stopped: 0
  graphDriverName: overlay
  graphOptions:
    overlay.ignore_chown_errors: "true"
    overlay.mount_program:
      Executable: /usr/local/bin/fuse-overlayfs
      Package: Unknown
      Version: |-
        fuse-overlayfs: version 1.12
        fusermount3 version: 3.15.1
        FUSE library version 3.15.1
        using FUSE kernel interface version 7.38
    overlay.mountopt: nodev,fsync=0
  graphRoot: /var/lib/containers/storage
  graphRootAllocated: 1564054310912
  graphRootUsed: 1449732149248
  graphStatus:
    Backing Filesystem: aufs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 0
  runRoot: /var/run/containers/storage
  transientStore: false
  volumePath: /var/lib/containers/storage/volumes
version:
  APIVersion: 4.6.1
  Built: 0
  BuiltTime: Thu Jan  1 01:00:00 1970
  GitCommit: ""
  GoVersion: go1.18.10
  Os: linux
  OsArch: linux/amd64
  Version: 4.6.1

#

Podman in a container

No

Privileged Or Rootless

Privileged

Upstream Latest Release

Yes

Additional environment details

No response

Additional information

Newb problems... I am new to containerisation... certain this is a config or installation problem my end.

[Luap99]

podman machine is only designed to run as rootless.

It is not clear what you are trying to do but on linux you can use podman natively and do not need to create a machine VM. The standard podman will run as root.

[DevilDogLinux]

@Luap99 - understood. Yes standard podman would be great! Didn't realise it cannot run as root.

Podman isn't in the Fatdog repo so I pulled various versions until I found one that executed.

I'm not looking for anything fancy ... just want "podman machine init" to run!

So - having created a podman user ...

 # su podman
 podman$ podman info
ERRO[0000] stat /root/.config/containers/storage.conf: permission denied 
podman$ 

I must have missed a configuration step?

[Luap99]

As said before you can run podman as root just fine, what you cannot do is run podman machine commands as root.

Setting up a proper rootless environment is more involved. I have no idea what your environment looks like but maybe it is easier to start on something that is known to work.

[DevilDogLinux]

Understood.

Yes - this is certainly a case of unusual environment and newb fever!

Fatdog is designed to run as root. This said I have added users for samba, mysql, apache ... and podman.

Have had a dig into the iso for another puppy linux that released with podman ...
https://forum.puppylinux.com/viewtopic.php?p=86462#p86462

Found alot of configuration that I was clearly missing.

Will RTFM but was hoping someone here was familiar with Fatdog or the other Puppies and had a (half) baked solution!

Found a version of podman-remote...

# ./podman-remote
./podman-remote: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by ./podman-remote)
./podman-remote: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by ./podman-remote)
./podman-remote: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by ./podman-remote)
# 
# ldd --version
ldd (GNU libc) 2.27
Copyright (C) 2018 Free Software Foundation, Inc...

That does not bode well!

: )

[DevilDogLinux]

su podman

export XDG_CONFIG_HOME="/home/podman/.config"
export XDG_RUNTIME_DIR="/home/podman/tmp"
export XDG_DATA_HOME="/home/podman/.local/share"
export XDG_CACHE_HOME="/home/podman/.cache"

podman machine init --disk-size 2

Downloading VM image: fedora-coreoDownloading VM image: fedora-coreos-38.20230902.2.1-qemu.x86_64.qcow2.xz [==========Downloading VM image: fedora-coreos-38.20230902.2.1-qemu.x86_64.qcow2.xz: done  
Extracting compressed file
Error: new disk size must be larger than current disk size: 10GB

Ooh! Basic functionality a-go-go!

Need to clear off some space but it seems podman ... is alive!!!

[DevilDogLinux]

Issue: "unable to start host networking: "stat /usr/libexec/podman/gvproxy: no such file or directory""
gvproxy not found?
Solution: locate a recent version of gvproxy:
https://github.com/containers/gvisor-tap-vsock/releases/tag/v0.7.0
File I got was called "gvproxy-linux"
copy to /usr/local/lib/podman
make a link to this file called "gvproxy"
ln -s gvproxy-linux gvproxy

Issue: "Error: open /etc/timezone: no such file or directory"
Solution: link to your zone file eg.
# ln -s /usr/share/zoneinfo/GB /etc/timezone
...

podman$ podman machine init hello-world
Extracting compressed file
Image resized.
Machine init complete
To start your machine run:

	podman machine start hello-world

podman$ podman machine start hello-world
Starting machine "hello-world"
Error: dial unix /home/podman/tmp/podman/qmp_hello-world.sock: connect: no such file or directory

ooh so close!

Issue: Error: dial unix /home/podman/tmp/podman/qmp_hello-world.sock: connect: no such file or directory
This one has me stumped.

podman$ podman init hello-world
WARN[0000] "/" is not a shared mount, this could cause issues or missing mounts with rootless containers 
ERRO[0000] cannot find UID/GID for user podman: no subuid ranges found for user "podman" in /etc/subuid - check rootless mode in man pages. 
WARN[0000] Using rootless single mapping into the namespace. This might break some images. Check /etc/subuid and /etc/subgid for adding sub*ids if not using a network user 
cannot chdir to /root: Permission denied
Error: setting up the process
podman$ 

I should deffo look thru the manuals ... plainly I have misapprehended the use of "podman machine" ... as @Luap99 tried to tell me.