Command & Conquer port failing to build because Docker not recognized to be running

Hello

as I come to learn that C&C has been ported by a fan to multiple systems, I was curious to install it on my machine.

The Github page seems simple enough

sudo pacman -S docker
sudo systemctl start docker
sudo usermod -aG docker $USER

then

# Clone repository
git clone https://github.com/fbraz3/GeneralsX.git
cd GeneralsX

# Build Zero Hour (GeneralsXZH) with Docker
./scripts/docker-build-linux-zh.sh linux64-deploy

# Binary location: build/linux64-deploy/GeneralsMD/GeneralsXZH

But when I try to build

❯ ./scripts/docker-build.sh linux64-deploy
======================================
  Generals Game Code - Linux Builder
======================================

[INFO] Checking dependencies...
[ERROR] Docker daemon is not running or you don't have permission.
  Try: sudo systemctl start docker
  Or add your user to the docker group: sudo usermod -aG docker $USER

this happens. I confirmed docker running with

docker run --rm hello-world

My user is part of the docker group, docker is running. What am I doing wrong?

inxi -Fazy
  Kernel: 7.1.2-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-7.1-x86_64
    root=UUID=84806755-713a-40f0-9fa2-c9b09f2fe665 rw udev.log_priority=3
    acpi_enforce_resources=lax
  Desktop: Sway v: 1.12 with: waybar tools: avail: swayidle vt: 1 dm: N/A
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: X570S AORUS MASTER v: -CF
    serial: <superuser required>
  Mobo: Gigabyte model: X570S AORUS MASTER serial: <superuser required>
    uuid: <superuser required> Firmware: UEFI vendor: American Megatrends LLC.
    v: F4 date: 12/26/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 3
    serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 0 microcode: 0xA20102E
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 12 threads: 24 tpc: 2
    smt: enabled cache: L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB
    desc: 12x512 KiB L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 3599 min/max: 567/4955 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 3599 2: 3599 3: 3599
    4: 3599 5: 3599 6: 3599 7: 3599 8: 3599 9: 3599 10: 3599 11: 3599 12: 3599
    13: 3599 14: 3599 15: 3599 16: 3599 17: 3599 18: 3599 19: 3599 20: 3599
    21: 3599 22: 3599 23: 3599 24: 3599 bogomips: 177605
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsa mitigation: Clear CPU buffers
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 48 [Radeon RX 9070/9070
    XT/9070 GRE] vendor: Tul / PowerColor driver: amdgpu v: kernel arch: RDNA-4
    code: Navi-4x process: TSMC n4 (4nm) built: 2025+ pcie: gen: 5
    speed: 32 GT/s lanes: 16 ports: active: DP-2,HDMI-A-1
    empty: DP-1,DP-3,Writeback-1 bus-ID: 0d:00.0 chip-ID: 1002:7550
    class-ID: 0300
  Display: wayland server: Xwayland v: 24.1.12 compositor: Sway v: 1.12
    driver: gpu: amdgpu d-rect: 5760x2160 display-ID: 1
  Monitor-1: DP-2 pos: right model: Gigabyte M32U serial: <filter>
    built: 2022 res: mode: 3840x2160 hz: 144 scale: 150% (1.5) to: 2560x1440
    dpi: 140 gamma: 1.2 size: 697x392mm (27.44x15.43") diag: 800mm (31.5")
    ratio: 16:9 modes: max: 3840x2160 min: 720x400
  Monitor-2: HDMI-A-1 pos: left model: EIZO NANAO EV2436W serial: <filter>
    built: 2013 res: mode: 1920x1200 hz: 60 scale: 100% (1) dpi: 94 gamma: 1.2
    size: 519x324mm (20.43x12.76") diag: 616mm (24.2") ratio: 16:10 modes:
    max: 1920x1200 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi wayland:
    drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.4-arch1.1 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon RX 9070 (radeonsi gfx1201 ACO DRM
    3.64 7.1.2-1-MANJARO) device-ID: 1002:7550 memory: 15.62 GiB unified: no
  API: Vulkan v: 1.4.350 layers: 6 device: 0 type: discrete-gpu name: AMD
    Radeon RX 9070 (RADV GFX1201) driver: mesa radv v: 26.1.4-arch1.1
    device-ID: 1002:7550 surfaces: N/A
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo gpu: amdgpu_top, lact,
    radeontop wl: swaymsg, wayland-info, wlr-randr x11: xprop,xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 48 HDMI/DP Audio
    driver: snd_hda_intel v: kernel pcie: gen: 5 speed: 32 GT/s lanes: 16
    bus-ID: 0d:00.1 chip-ID: 1002:ab40 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 0f:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k7.1.2-1-MANJARO status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.6.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 06:00.0
    chip-ID: 8086:2725 class-ID: 0280
  IF: wlp6s0 state: down mac: <filter>
  Device-2: Intel Ethernet I225-V vendor: Gigabyte driver: igc v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 07:00.0
    chip-ID: 8086:15f3 class-ID: 0200
  IF: enp7s0 state: up speed: 2500 Mbps duplex: full mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  IF-ID-2: vpnnl1 state: unknown speed: N/A duplex: N/A mac: N/A
  Info: services: sshd,systemd-timesyncd
Bluetooth:
  Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 5-5:2 chip-ID: 8087:0032
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: see --recommends
Drives:
  Local Storage: total: 6.46 TiB used: 3.47 TiB (53.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:5 vendor: Lexar model: SSD NM790 4TB
    size: 3.73 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 12237 temp: 54.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung
    model: SSD 970 EVO Plus 2TB size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 45.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000MX500SSD1
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 023 scheme: GPT
Partition:
  ID-1: / raw-size: 200 GiB size: 199.85 GiB (99.93%) used: 31.9 GiB (16.0%)
    fs: xfs dev: /dev/nvme0n1p3 maj-min: 259:8
  ID-2: /boot/efi raw-size: 1024 MiB size: 1022 MiB (99.80%)
    used: 336 KiB (0.0%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:6
  ID-3: /home raw-size: 3.49 TiB size: 3.49 TiB (99.95%)
    used: 2.57 TiB (73.7%) fs: xfs dev: /dev/nvme0n1p4 maj-min: 259:9
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 38 GiB used: 0 KiB (0.0%) priority: -1
    dev: /dev/nvme0n1p2 maj-min: 259:7
Sensors:
  System Temperatures: cpu: 44.4 C mobo: 40.0 C gpu: amdgpu temp: 33.0 C
    mem: 33.0 C
  Fan Speeds (rpm): fan-1: 0 fan-2: 1062 fan-3: 772 gpu: amdgpu fan: 0
  Power: 12v: N/A 5v: N/A 3.3v: N/A vbat: 3.03 gpu: amdgpu watts: 21.00
Info:
  Memory: total: 32 GiB available: 31.23 GiB used: 14.13 GiB (45.2%)
  Processes: 561 Power: uptime: 11h 38m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.44 GiB services: upowerd Init: systemd
    v: 261 default: graphical tool: systemctl
  Packages: 1139 pm: pacman pkgs: 1128 libs: 375 tools: yay pm: flatpak
    pkgs: 11 Compilers: gcc: 16.1.1 Shell: Zsh v: 5.9.1 running-in: alacritty
    inxi: 3.3.41```
1 Like

sudo systemctl start docker
[/quote]

is not a very good command the correct one is `sudo systemctl enable --now docker

Thx for the answer

I contemplated this option but as I only want to run a game, not a service, I don’t want docker to be running all the time. I’d start docker only as need be to run the game.

Did you reboot after that command? It won’t take effect until you do.

It worked. Curious enough after advice I would have suspected in ye old Windows days. Just reboot.

Wouldn’t there have been a command that should have done this, or would a logout have been enough?

That’s fine too. (Technically, you just need a new shell after the change.)

There is a couple of methods which do not involve a full system restart

A change in user’s group membership will only take effect after sign-off and sign-on.

Another method is systemctl soft-reboot which will restart userspace and you will be required to login. It is often faster than clicking around with the mouse.

A service can be started with or without sudo. The system will popup an authorisation dialog if run with out sudo.

A manually started system service (systemctl start <service>) will not persist after reboot - this comes as a surprise to some :slight_smile:

3 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.