Anyone running Docker on FD64?

[devildog]

Hi guys!

Have tried to get docker running on FD before with mixed results back in 2021.
Old thread on the docker forums here:
https://forums.docker.com/t/lf-carry-ne ... ker/111416

Has anyone got this working right?

Have pulled and converted docker-desktop.deb (rt click convert).

RtClick installed the resulting file (docker-desktop-4.23.0_120376-amd64-DEB.txz)

copied "docker" command from the .tarball /usr/local/bin -> /usr/bin/docker to stop an error.

However the docker desktop is not running up - just burns resources until the machine is overloaded.

Any other way round appreciated! Interested in how you got containers running. Would prefer docker.

[devildog]

Had a pop with podman...

(edit)

podman-remote-static-linux_amd64.tar.gz
^^ this was the wrong package!

https://github.com/mgoltzsche/podman-st ... d64.tar.gz
I suspect this is the correct one because it has configs etc.
Will try again... see next post if I get anywhere!

dropped the executable into /usr/bin

Code: Select all

# whereis podman
podman: /usr/bin/podman

# 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

Tried running as spot however ran into permissions problems as much of the config seems to be hard coded to be at /root/.config ...

More luck with podman desktop - that ran up without apparent issues but ofc cannot manage containers.

Podman Desktop

podman-desktop.jpg (64.67 KiB) Viewed 1290 times

... and with the following errors in output ...

Code: Select all

# ./podman-desktop --no-sandbox
[30126:0917/090407.899638:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[30126:0917/090407.899718:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[30126:0917/090408.188928:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[30126:0917/090408.214727:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[30126:0917/090408.254550:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
Kubeconfig path /root/.kube/config provided does not exist. Skipping.
System ready. Loading extensions...
[30126:0917/090408.740286:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: 
Activating extension (podman-desktop.compose)
Activating extension (podman-desktop.docker)
Activating extension (podman-desktop.kind)
Activating extension (podman-desktop.kube-context)
[kube-context] starting extension kube-context
Activating extension (podman-desktop.lima)
[lima] Could not find socket at /root/.lima/podman/sock/podman.sock
[lima] Could not find config at /root/.lima/podman/copied-from-guest/kubeconfig.yaml
Activating extension (podman-desktop.podman)
Activating extension (podman-desktop.registries)
Activating extension (podman-desktop.compose) ended
Activating extension (podman-desktop.docker) ended
Activating extension (podman-desktop.kube-context) ended
Activating extension (podman-desktop.lima) ended
Unable to fetch the available extensions: Timeout awaiting 'lookup' for 1000ms
[podman] Error while pinging docker as podman Error: connect ENOENT /var/run/docker.sock
    at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'connect',
  address: '/var/run/docker.sock'
}
Activating extension (podman-desktop.registries) ended
[kind] Error: Error: spawn kind-linux-amd64 ENOENT
    at ChildProcess.<anonymous> (/opt/podman-desktop-1.3.1/resources/app.asar/extensions/kind/builtin/kind.cdix/dist/extension.js:7:11545)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1091:16)
    at Socket.<anonymous> (node:internal/child_process:449:11)
    at Socket.emit (node:events:513:28)
    at Pipe.<anonymous> (node:net:322:12)
Activating extension (podman-desktop.kind) ended
PluginSystem: received dom-ready event from the UI
Delayed startup, flushing 37 events
Unable to fetch the available extensions: unable to get local issuer certificate
Unable to fetch the available extensions: unable to get local issuer certificate
[podman] Podman extension: Could not find the socket at /run/user/0/podman/podman.sock after 5s. The command podman system service --time=0 did not work to start the podman socket.
Activating extension (podman-desktop.podman) ended
PluginSystem: initialization done.
Autostarting container engine
Unable to fetch the available extensions: unable to get local issuer certificate

[devildog]

https://github.com/mgoltzsche/podman-st ... d64.tar.gz

Code: Select all

# podman machine init --disk-size 2
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
# 

Now this is odd because iirc podman is supposed to run as root.
Will try setting up a user for it....

(edit)

...make a user with a home but no pw

Code: Select all

# adduser -D podman

...perm problems in the temp folder so...

Code: Select all

# chown -R podman:root /tmp/runtime-root

... swap user and try a command ...

Code: Select all

# su podman
podman$ podman machine init --disk-size 2
ERRO[0000] stat /root/.config/containers/storage.conf: permission denied 

doh! Can't actually set viable perms for that path... the journey continues.

[devildog]

Posted an outline on podman's GIT.

https://github.com/containers/podman/issues/20008

Baby steps - podman info now works!

Code: Select all

# 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

#

[devildog]

Code: Select all

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!!!

[jamesbond]

Thank you for sharing, devildog!

I've never personally run docker in Fatdog64, but I'm interested to know how. It might come handy later.

Keep on going, please.

[devildog]

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-ta ... 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

Code: Select all

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$ 

Issue: "/" is not a shared mount, this could cause issues or missing mounts with rootless containers
This one currently has me stumped. Clearly needs more config.

[step]

Code: Select all

ERRO[0000] cannot find UID/GID for user podman

seems to imply that you need to create a user "podman" and a group "podman", I don't know that the rest of the line that refers to /etc/subid means. Maybe it's some configuration file brought in by podman itself.