Falha ao instalar imagem WinBoat - MX-Linux

italo.rp · Janeiro 19, 2026, 12:04pm

Boa tarde,

procurei, mas não achei.

Estou no MX no momento, estou tentando usar o Winboat para instalar o Windows.

Já tentei todas as soluções que procurei, mas não obtive sucesso. Qual saída de log preciso enviar pra vocês aqui tentarem me ajudar? rs

A máquina simplesmente fala que houve um erro, mas não detalha muito e o log que apresentou, já fiz de tudo para sanar os problemas dele, algumas vezes fala até que foi resolvido, mas não consegue instalar. Outra coisa é que o Daemon do docker não inicia, já tentei iniciar manualmente ou “nível grub”, mas até agora nada.

Alguma dica?

Ks_Uwhwh · Janeiro 19, 2026, 4:01pm

Então já resolveu

italo.rp · Janeiro 19, 2026, 4:30pm

Não kkkk
Não inicia o daemon e quando inicia, o próximo passo da sempre o mesmo erro. O Winboat fala que houve um erro.

LinuxUser · Janeiro 19, 2026, 4:33pm

Qual é o log?

italo.rp · Janeiro 19, 2026, 4:34pm

Docker quase sempre dá problemas, poucas vezes o Daemon sobe.

O Podman eu consigo prosseguir. Mas ele sempre falha

As instruções no “these” instructions não resolve (If your WinBoat installation has failed and you might know why, follow these steps to clean up an...)

LinuxUser · Janeiro 19, 2026, 4:36pm

Faz o que ele falou, checa os logs e posta aqui, deve ter alguma indicação do problema lá.

italo.rp · Janeiro 19, 2026, 4:38pm

Essa questão do “no container with name od ID Winboat found não é algo que eu consegui resolver muito bem. Porque eu fiz algumas coisas que pedem para checar se tão container existe, ele diz que existe na saída (não lembro os comandos), mas ao tentar iniciar, acontece a falha.

2026-01-12 17:55:28 | INFO | Wrote to compose file at: /home/user/.winboat/docker-compose.yml
2026-01-12 17:55:29 | INFO | Compose file content: “name: winboat\nvolumes:\n  data:\nservices:\n  windows:\n    image: ghcr.io/dockur/windows:5.14\n    container_name: WinBoat\n    environment:\n      VERSION: custom\n      RAM_SIZE: 4G\n      CPU_CORES: “2”\n      DISK_SIZE: 32G\n      USERNAME: userregis\n      PASSWORD: asdqwe123\n      HOME: ${HOME}\n      LANGUAGE: English\n      USER_PORTS: “7148”\n      HOST_PORTS: “7149”\n      ARGUMENTS: -qmp tcp:0.0.0.0:7149,server,wait=off\n    cap_add:\n      - NET_ADMIN\n    privileged: true\n    ports:\n      - 127.0.0.1:47270-47279:8006\n      - 127.0.0.1:47280-47289:7148\n      - 127.0.0.1:47290-47299:7149\n      - 127.0.0.1:47300-47309:3389/tcp\n      - 127.0.0.1:47310-47319:3389/udp\n    stop_grace_period: 120s\n    restart: on-failure\n    volumes:\n      - /home/user/winboat:/storage\n      - /dev/bus/usb:/dev/bus/usb\n      - ./oem:/oem\n      - /home/user/Documentos/Windows 10.iso:/boot.iso\n    devices:\n      - /dev/kvm\n”
2026-01-12 17:55:29 | ERROR | Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
e[4m>>>> Executing external compose provider “/usr/bin/podman-compose”. Please see podman-compose(1) for how to disable this message. <<<<

e[0mError: host and container port ranges have different lengths: 10 vs 1
Error: no container with name or ID “WinBoat” found: no such container

2026-01-12 17:55:29 | ERROR | Failed to run container action ‘docker  port  WinBoat’
2026-01-12 17:55:29 | ERROR | Error: Command failed: docker port WinBoat
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: no container with name or ID “WinBoat” found: no such container

2026-01-12 17:58:07 | INFO | Wrote to compose file at: /home/user/.winboat/podman-compose.yml
2026-01-12 17:58:07 | INFO | Compose file content: “name: winboat\nvolumes:\n  data:\nservices:\n  windows:\n    image: ghcr.io/dockur/windows:5.14\n    container_name: WinBoat\n    environment:\n      VERSION: custom\n      RAM_SIZE: 4G\n      CPU_CORES: “2”\n      DISK_SIZE: 32G\n      USERNAME: userregis\n      PASSWORD: asdqwe123\n      HOME: ${HOME}\n      LANGUAGE: English\n      NETWORK: user\n      USER_PORTS: “7148”\n      HOST_PORTS: “7149”\n      ARGUMENTS: -qmp tcp:0.0.0.0:7149,server,wait=off\n    cap_add:\n      - NET_ADMIN\n    ports:\n      - 127.0.0.1::8006\n      - 127.0.0.1::7148\n      - 127.0.0.1::7149\n      - 127.0.0.1::3389/tcp\n      - 127.0.0.1::3389/udp\n    stop_grace_period: 120s\n    restart: on-failure\n    privileged: true\n    volumes:\n      - /home/user/winboat:/storage\n      - ./oem:/oem\n      - /home/user/Documentos/Windows 10.iso:/boot.iso\n    devices:\n      - /dev/kvm\n      - /dev/bus/usb\n”
2026-01-12 17:58:50 | ERROR | Trying to pull ghcr.io/dockur/windows:5.14…
Getting image source signatures
Copying blob sha256:3cc25670ac64453da50b2725669d384f1df5988bf22128c23a6e17fe6b7ed1b6
Copying blob sha256:7e003ed514ae6d274a9d5b27c7275bb013f8ff808eb8315c954e955311942dcc
Copying blob sha256:35b42edd534911c77664516d9e0f10823bd30669f774bb818b966b5d2338da9d
Copying blob sha256:d9ad3d8dc9e09f5fc3cdc644e845a1081cd06d07a8ca952765c62756f4b5c6f1
Copying blob sha256:1e289d7526b8c33abb5c639662526285a70fc485cbd62a6a4de56241508f5126
Copying blob sha256:a221a87e4fff6c28a776b0b4d28ac285df71f26b18143b5fa3f659b8102f3493
Error: copying system image from manifest list: writing blob: adding layer with blob “sha256:a221a87e4fff6c28a776b0b4d28ac285df71f26b18143b5fa3f659b8102f3493”/“”/“sha256:686bbe61e29a9e013e322e934151af3315d67ff5ff7748780e2e08f5ceb2f875”: unpacking failed (error: exit status 1; output: potentially insufficient UIDs or GIDs available in user namespace (requested 0:42 for /etc/gshadow): Check /etc/subuid and /etc/subgid if configured locally and run “podman system migrate”: lchown /etc/gshadow: invalid argument)
Error: no container with name or ID “WinBoat” found: no such container

2026-01-12 17:58:50 | ERROR | Failed to run container action ‘podman  port  WinBoat’
2026-01-12 17:58:50 | ERROR | Error: Command failed: podman port WinBoat
Error: no container with name or ID “WinBoat” found: no such container

2026-01-12 18:25:24 | INFO | Wrote to compose file at: /home/user/.winboat/docker-compose.yml
2026-01-12 18:25:24 | INFO | Compose file content: “name: winboat\nvolumes:\n  data:\nservices:\n  windows:\n    image: ghcr.io/dockur/windows:5.14\n    container_name: WinBoat\n    environment:\n      VERSION: “10”\n      RAM_SIZE: 3G\n      CPU_CORES: “2”\n      DISK_SIZE: 32G\n      USERNAME: userregis\n      PASSWORD: asdqwe123\n      HOME: ${HOME}\n      LANGUAGE: English\n      USER_PORTS: “7148”\n      HOST_PORTS: “7149”\n      ARGUMENTS: -qmp tcp:0.0.0.0:7149,server,wait=off\n    cap_add:\n      - NET_ADMIN\n    privileged: true\n    ports:\n      - 127.0.0.1:47270-47279:8006\n      - 127.0.0.1:47280-47289:7148\n      - 127.0.0.1:47290-47299:7149\n      - 127.0.0.1:47300-47309:3389/tcp\n      - 127.0.0.1:47310-47319:3389/udp\n    stop_grace_period: 120s\n    restart: on-failure\n    volumes:\n      - /home/user/winboat:/storage\n      - /dev/bus/usb:/dev/bus/usb\n      - ./oem:/oem\n    devices:\n      - /dev/kvm\n”
2026-01-12 18:25:25 | ERROR | Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
e[4m>>>> Executing external compose provider “/usr/bin/podman-compose”. Please see podman-compose(1) for how to disable this message. <<<<

e[0mError: host and container port ranges have different lengths: 10 vs 1
Error: no container with name or ID “WinBoat” found: no such container

2026-01-12 18:25:25 | ERROR | Failed to run container action ‘docker  port  WinBoat’
2026-01-12 18:25:25 | ERROR | Error: Command failed: docker port WinBoat
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: no container with name or ID “WinBoat” found: no such container

2026-01-12 18:44:11 | INFO | Wrote to compose file at: /home/user/.winboat/podman-compose.yml
2026-01-12 18:44:11 | INFO | Compose file content: “name: winboat\nvolumes:\n  data:\nservices:\n  windows:\n    image: ghcr.io/dockur/windows:5.14\n    container_name: WinBoat\n    environment:\n      VERSION: “10”\n      RAM_SIZE: 3G\n      CPU_CORES: “2”\n      DISK_SIZE: 32G\n      USERNAME: userregis\n      PASSWORD: asdqwe123\n      HOME: ${HOME}\n      LANGUAGE: English\n      NETWORK: user\n      USER_PORTS: “7148”\n      HOST_PORTS: “7149”\n      ARGUMENTS: -qmp tcp:0.0.0.0:7149,server,wait=off\n    cap_add:\n      - NET_ADMIN\n    ports:\n      - 127.0.0.1::8006\n      - 127.0.0.1::7148\n      - 127.0.0.1::7149\n      - 127.0.0.1::3389/tcp\n      - 127.0.0.1::3389/udp\n    stop_grace_period: 120s\n    restart: on-failure\n    privileged: true\n    volumes:\n      - /home/user/winboat:/storage\n      - ./oem:/oem\n    devices:\n      - /dev/kvm\n      - /dev/bus/usb\n”
2026-01-12 18:44:54 | ERROR | Trying to pull ghcr.io/dockur/windows:5.14…
Getting image source signatures
Copying blob sha256:3cc25670ac64453da50b2725669d384f1df5988bf22128c23a6e17fe6b7ed1b6
Copying blob sha256:1e289d7526b8c33abb5c639662526285a70fc485cbd62a6a4de56241508f5126
Copying blob sha256:7e003ed514ae6d274a9d5b27c7275bb013f8ff808eb8315c954e955311942dcc
Copying blob sha256:d9ad3d8dc9e09f5fc3cdc644e845a1081cd06d07a8ca952765c62756f4b5c6f1
Copying blob sha256:a221a87e4fff6c28a776b0b4d28ac285df71f26b18143b5fa3f659b8102f3493
Copying blob sha256:35b42edd534911c77664516d9e0f10823bd30669f774bb818b966b5d2338da9d
Error: copying system image from manifest list: writing blob: adding layer with blob “sha256:a221a87e4fff6c28a776b0b4d28ac285df71f26b18143b5fa3f659b8102f3493”/“”/“sha256:686bbe61e29a9e013e322e934151af3315d67ff5ff7748780e2e08f5ceb2f875”: unpacking failed (error: exit status 1; output: potentially insufficient UIDs or GIDs available in user namespace (requested 0:42 for /etc/gshadow): Check /etc/subuid and /etc/subgid if configured locally and run “podman system migrate”: lchown /etc/gshadow: invalid argument)
Error: no container with name or ID “WinBoat” found: no such container

2026-01-12 18:44:54 | ERROR | Failed to run container action ‘podman  port  WinBoat’
2026-01-12 18:44:54 | ERROR | Error: Command failed: podman port WinBoat
Error: no container with name or ID “WinBoat” found: no such container

2026-01-12 18:47:27 | INFO | Wrote to compose file at: /home/user/.winboat/docker-compose.yml
2026-01-12 18:47:27 | INFO | Compose file content: “name: winboat\nvolumes:\n  data:\nservices:\n  windows:\n    image: ghcr.io/dockur/windows:5.14\n    container_name: WinBoat\n    environment:\n      VERSION: custom\n      RAM_SIZE: 3G\n      CPU_CORES: “2”\n      DISK_SIZE: 32G\n      USERNAME: userregis\n      PASSWORD: “1234”\n      HOME: ${HOME}\n      LANGUAGE: English\n      USER_PORTS: “7148”\n      HOST_PORTS: “7149”\n      ARGUMENTS: -qmp tcp:0.0.0.0:7149,server,wait=off\n    cap_add:\n      - NET_ADMIN\n    privileged: true\n    ports:\n      - 127.0.0.1:47270-47279:8006\n      - 127.0.0.1:47280-47289:7148\n      - 127.0.0.1:47290-47299:7149\n      - 127.0.0.1:47300-47309:3389/tcp\n      - 127.0.0.1:47310-47319:3389/udp\n    stop_grace_period: 120s\n    restart: on-failure\n    volumes:\n      - /home/user/winboat:/storage\n      - /dev/bus/usb:/dev/bus/usb\n      - ./oem:/oem\n      - /home/user/Documentos/Windows 10.iso:/boot.iso\n    devices:\n      - /dev/kvm\n”
2026-01-12 18:47:27 | ERROR | Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
e[4m>>>> Executing external compose provider “/usr/bin/podman-compose”. Please see podman-compose(1) for how to disable this message. <<<<

e[0mError: host and container port ranges have different lengths: 10 vs 1
Error: no container with name or ID “WinBoat” found: no such container

2026-01-12 18:47:27 | ERROR | Failed to run container action ‘docker  port  WinBoat’
2026-01-12 18:47:27 | ERROR | Error: Command failed: docker port WinBoat
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: no container with name or ID “WinBoat” found: no such container

2026-01-12 19:12:24 | INFO | Wrote to compose file at: /home/user/.winboat/docker-compose.yml
2026-01-12 19:12:24 | INFO | Compose file content: “name: winboat\nvolumes:\n  data:\nservices:\n  windows:\n    image: ghcr.io/dockur/windows:5.14\n    container_name: WinBoat\n    environment:\n      VERSION: “10”\n      RAM_SIZE: 3G\n      CPU_CORES: “2”\n      DISK_SIZE: 32G\n      USERNAME: userregis\n      PASSWORD: “1234”\n      HOME: ${HOME}\n      LANGUAGE: English\n      USER_PORTS: “7148”\n      HOST_PORTS: “7149”\n      ARGUMENTS: -qmp tcp:0.0.0.0:7149,server,wait=off\n    cap_add:\n      - NET_ADMIN\n    privileged: true\n    ports:\n      - 127.0.0.1:47270-47279:8006\n      - 127.0.0.1:47280-47289:7148\n      - 127.0.0.1:47290-47299:7149\n      - 127.0.0.1:47300-47309:3389/tcp\n      - 127.0.0.1:47310-47319:3389/udp\n    stop_grace_period: 120s\n    restart: on-failure\n    volumes:\n      - /home/user/winboat:/storage\n      - /dev/bus/usb:/dev/bus/usb\n      - ./oem:/oem\n    devices:\n      - /dev/kvm\n”
2026-01-12 19:12:24 | ERROR | Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
e[4m>>>> Executing external compose provider “/usr/bin/podman-compose”. Please see podman-compose(1) for how to disable this message. <<<<

e[0mError: host and container port ranges have different lengths: 10 vs 1
Error: no container with name or ID “WinBoat” found: no such container

2026-01-12 19:12:24 | ERROR | Failed to run container action ‘docker  port  WinBoat’
2026-01-12 19:12:24 | ERROR | Error: Command failed: docker port WinBoat
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: no container with name or ID “WinBoat” found: no such container

2026-01-12 19:52:18 | ERROR | Failed to get container status, is Docker installed?
2026-01-12 19:52:18 | ERROR | Error: spawn docker ENOENT
2026-01-12 19:53:23 | ERROR | Failed to get container status, is Docker installed?
2026-01-12 19:53:23 | ERROR | Error: Command failed: docker ps -a --filter name=WinBoat --format {{.Names}}
Cannot connect to the Docker daemon at unix:///run/user/111269/podman/podman.sock. Is the docker daemon running?

2026-01-12 19:56:25 | ERROR | Failed to get container status, is Docker installed?
2026-01-12 19:56:25 | ERROR | Error: Command failed: docker ps -a --filter name=WinBoat --format {{.Names}}
Cannot connect to the Docker daemon at unix:///run/user/111269/podman/podman.sock. Is the docker daemon running?

2026-01-12 20:29:07 | ERROR | Failed to get container status, is Docker installed?
2026-01-12 20:29:07 | ERROR | Error: Command failed: docker ps -a --filter name=WinBoat --format {{.Names}}
failed to connect to the docker API at unix:///run/user/111269/podman/podman.sock; check if the path is correct and if the daemon is running: dial unix /run/user/111269/podman/podman.sock: connect: no such file or directory

2026-01-13 10:27:04 | ERROR | Failed to get container status, is Docker installed?
2026-01-13 10:27:04 | ERROR | Error: Command failed: docker ps -a --filter name=WinBoat --format {{.Names}}
failed to connect to the docker API at unix:///run/user/111269/podman/podman.sock; check if the path is correct and if the daemon is running: dial unix /run/user/111269/podman/podman.sock: connect: no such file or directory

2026-01-15 11:26:03 | ERROR | Failed to get container status, is Docker installed?
2026-01-15 11:26:03 | ERROR | Error: Command failed: docker ps -a --filter name=WinBoat --format {{.Names}}
failed to connect to the docker API at unix:///run/user/111269/podman/podman.sock; check if the path is correct and if the daemon is running: dial unix /run/user/111269/podman/podman.sock: connect: no such file or directory

2026-01-15 20:45:10 | ERROR | Failed to get container status, is Docker installed?
2026-01-15 20:45:10 | ERROR | Error: Command failed: docker ps -a --filter name=WinBoat --format {{.Names}}
failed to connect to the docker API at unix:///run/user/111269/podman/podman.sock; check if the path is correct and if the daemon is running: dial unix /run/user/111269/podman/podman.sock: connect: no such file or directory

2026-01-15 20:45:22 | ERROR | Failed to get container status, is Docker installed?
2026-01-15 20:45:22 | ERROR | Error: Command failed: docker ps -a --filter name=WinBoat --format {{.Names}}
failed to connect to the docker API at unix:///run/user/111269/podman/podman.sock; check if the path is correct and if the daemon is running: dial unix /run/user/111269/podman/podman.sock: connect: no such file or directory

2026-01-15 20:45:53 | INFO | Wrote to compose file at: /home/user/.winboat/podman-compose.yml
2026-01-15 20:45:53 | INFO | Compose file content: “name: winboat\nvolumes:\n  data:\nservices:\n  windows:\n    image: ghcr.io/dockur/windows:5.14\n    container_name: WinBoat\n    environment:\n      VERSION: “10”\n      RAM_SIZE: 3G\n      CPU_CORES: “2”\n      DISK_SIZE: 32G\n      USERNAME: userregis\n      PASSWORD: asdqwe123\n      HOME: ${HOME}\n      LANGUAGE: English\n      NETWORK: user\n      USER_PORTS: “7148”\n      HOST_PORTS: “7149”\n      ARGUMENTS: -qmp tcp:0.0.0.0:7149,server,wait=off\n    cap_add:\n      - NET_ADMIN\n    ports:\n      - 127.0.0.1::8006\n      - 127.0.0.1::7148\n      - 127.0.0.1::7149\n      - 127.0.0.1::3389/tcp\n      - 127.0.0.1::3389/udp\n    stop_grace_period: 120s\n    restart: on-failure\n    privileged: true\n    volumes:\n      - /home/user/winboat:/storage\n      - ./oem:/oem\n    devices:\n      - /dev/kvm\n      - /dev/bus/usb\n”
2026-01-15 20:46:41 | ERROR | Trying to pull ghcr.io/dockur/windows:5.14…
Getting image source signatures
Copying blob sha256:3cc25670ac64453da50b2725669d384f1df5988bf22128c23a6e17fe6b7ed1b6
Copying blob sha256:d9ad3d8dc9e09f5fc3cdc644e845a1081cd06d07a8ca952765c62756f4b5c6f1
Copying blob sha256:7e003ed514ae6d274a9d5b27c7275bb013f8ff808eb8315c954e955311942dcc
Copying blob sha256:1e289d7526b8c33abb5c639662526285a70fc485cbd62a6a4de56241508f5126
Copying blob sha256:35b42edd534911c77664516d9e0f10823bd30669f774bb818b966b5d2338da9d
Copying blob sha256:a221a87e4fff6c28a776b0b4d28ac285df71f26b18143b5fa3f659b8102f3493
Error: copying system image from manifest list: writing blob: adding layer with blob “sha256:a221a87e4fff6c28a776b0b4d28ac285df71f26b18143b5fa3f659b8102f3493”/“”/“sha256:686bbe61e29a9e013e322e934151af3315d67ff5ff7748780e2e08f5ceb2f875”: unpacking failed (error: exit status 1; output: potentially insufficient UIDs or GIDs available in user namespace (requested 0:42 for /etc/gshadow): Check /etc/subuid and /etc/subgid if configured locally and run “podman system migrate”: lchown /etc/gshadow: invalid argument)
Error: no container with name or ID “WinBoat” found: no such container

2026-01-15 20:46:41 | ERROR | Failed to run container action ‘podman  port  WinBoat’
2026-01-15 20:46:41 | ERROR | Error: Command failed: podman port WinBoat
Error: no container with name or ID “WinBoat” found: no such container

2026-01-19 11:46:16 | INFO | Wrote to compose file at: /home/user/.winboat/podman-compose.yml
2026-01-19 11:46:16 | INFO | Compose file content: “name: winboat\nvolumes:\n  data:\nservices:\n  windows:\n    image: ghcr.io/dockur/windows:5.14\n    container_name: WinBoat\n    environment:\n      VERSION: “10”\n      RAM_SIZE: 3G\n      CPU_CORES: “2”\n      DISK_SIZE: 32G\n      USERNAME: userregis\n      PASSWORD: asdqwe123\n      HOME: ${HOME}\n      LANGUAGE: English\n      NETWORK: user\n      USER_PORTS: “7148”\n      HOST_PORTS: “7149”\n      ARGUMENTS: -qmp tcp:0.0.0.0:7149,server,wait=off\n    cap_add:\n      - NET_ADMIN\n    ports:\n      - 127.0.0.1::8006\n      - 127.0.0.1::7148\n      - 127.0.0.1::7149\n      - 127.0.0.1::3389/tcp\n      - 127.0.0.1::3389/udp\n    stop_grace_period: 120s\n    restart: on-failure\n    privileged: true\n    volumes:\n      - /home/user/winboat:/storage\n      - ./oem:/oem\n    devices:\n      - /dev/kvm\n      - /dev/bus/usb\n”
2026-01-19 11:47:05 | ERROR | Trying to pull ghcr.io/dockur/windows:5.14…
Getting image source signatures
Copying blob sha256:3cc25670ac64453da50b2725669d384f1df5988bf22128c23a6e17fe6b7ed1b6
Copying blob sha256:35b42edd534911c77664516d9e0f10823bd30669f774bb818b966b5d2338da9d
Copying blob sha256:1e289d7526b8c33abb5c639662526285a70fc485cbd62a6a4de56241508f5126
Copying blob sha256:a221a87e4fff6c28a776b0b4d28ac285df71f26b18143b5fa3f659b8102f3493
Copying blob sha256:d9ad3d8dc9e09f5fc3cdc644e845a1081cd06d07a8ca952765c62756f4b5c6f1
Copying blob sha256:7e003ed514ae6d274a9d5b27c7275bb013f8ff808eb8315c954e955311942dcc
Error: copying system image from manifest list: writing blob: adding layer with blob “sha256:a221a87e4fff6c28a776b0b4d28ac285df71f26b18143b5fa3f659b8102f3493”/“”/“sha256:686bbe61e29a9e013e322e934151af3315d67ff5ff7748780e2e08f5ceb2f875”: unpacking failed (error: exit status 1; output: potentially insufficient UIDs or GIDs available in user namespace (requested 0:42 for /etc/gshadow): Check /etc/subuid and /etc/subgid if configured locally and run “podman system migrate”: lchown /etc/gshadow: invalid argument)
Error: no container with name or ID “WinBoat” found: no such container

2026-01-19 11:47:06 | ERROR | Failed to run container action ‘podman  port  WinBoat’
2026-01-19 11:47:06 | ERROR | Error: Command failed: podman port WinBoat
Error: no container with name or ID “WinBoat” found: no such container

2026-01-19 16:33:15 | INFO | Wrote to compose file at: /home/user/.winboat/podman-compose.yml
2026-01-19 16:33:15 | INFO | Compose file content: “name: winboat\nvolumes:\n  data:\nservices:\n  windows:\n    image: ghcr.io/dockur/windows:5.14\n    container_name: WinBoat\n    environment:\n      VERSION: “11”\n      RAM_SIZE: 4G\n      CPU_CORES: “2”\n      DISK_SIZE: 32G\n      USERNAME: userregis\n      PASSWORD: asdqwe123\n      HOME: ${HOME}\n      LANGUAGE: English\n      NETWORK: user\n      USER_PORTS: “7148”\n      HOST_PORTS: “7149”\n      ARGUMENTS: -qmp tcp:0.0.0.0:7149,server,wait=off\n    cap_add:\n      - NET_ADMIN\n    ports:\n      - 127.0.0.1::8006\n      - 127.0.0.1::7148\n      - 127.0.0.1::7149\n      - 127.0.0.1::3389/tcp\n      - 127.0.0.1::3389/udp\n    stop_grace_period: 120s\n    restart: on-failure\n    privileged: true\n    volumes:\n      - /home/user/winboat:/storage\n      - ./oem:/oem\n    devices:\n      - /dev/kvm\n      - /dev/bus/usb\n”
2026-01-19 16:33:56 | ERROR | Trying to pull ghcr.io/dockur/windows:5.14…
Getting image source signatures
Copying blob sha256:3cc25670ac64453da50b2725669d384f1df5988bf22128c23a6e17fe6b7ed1b6
Copying blob sha256:1e289d7526b8c33abb5c639662526285a70fc485cbd62a6a4de56241508f5126
Copying blob sha256:7e003ed514ae6d274a9d5b27c7275bb013f8ff808eb8315c954e955311942dcc
Copying blob sha256:d9ad3d8dc9e09f5fc3cdc644e845a1081cd06d07a8ca952765c62756f4b5c6f1
Copying blob sha256:35b42edd534911c77664516d9e0f10823bd30669f774bb818b966b5d2338da9d
Copying blob sha256:a221a87e4fff6c28a776b0b4d28ac285df71f26b18143b5fa3f659b8102f3493
Error: copying system image from manifest list: writing blob: adding layer with blob “sha256:a221a87e4fff6c28a776b0b4d28ac285df71f26b18143b5fa3f659b8102f3493”/“”/“sha256:686bbe61e29a9e013e322e934151af3315d67ff5ff7748780e2e08f5ceb2f875”: unpacking failed (error: exit status 1; output: potentially insufficient UIDs or GIDs available in user namespace (requested 0:42 for /etc/gshadow): Check /etc/subuid and /etc/subgid if configured locally and run “podman system migrate”: lchown /etc/gshadow: invalid argument)
Error: no container with name or ID “WinBoat” found: no such container

2026-01-19 16:33:57 | ERROR | Failed to run container action ‘podman  port  WinBoat’
2026-01-19 16:33:57 | ERROR | Error: Command failed: podman port WinBoat
Error: no container with name or ID “WinBoat” found: no such container

LinuxUser · Janeiro 19, 2026, 4:47pm

Siga essa documentação, adicione o repositório que ela pede aqui e tente executar o WinBoat novamente.

Add Docker’s official GPG key:

sudo apt update

sudo apt install ca-certificates curl

sudo install -m 0755 -d /etc/apt/keyrings

sudo curl -fsSL ``https://download.docker.com/linux/debian/gpg`` -o /etc/apt/keyrings/docker.asc

sudo chmod a+r /etc/apt/keyrings/docker.asc

Add the repository to Apt sources:

sudo tee /etc/apt/sources.list.d/docker.sources <<EOF
Types: deb
URIs: https://download.docker.com/linux/debian
Suites: $(. /etc/os-release && echo "$VERSION_CODENAME")
Components: stable
Signed-By: /etc/apt/keyrings/docker.asc
EOF

sudo apt update

Depois disso, executa esses comandos:

sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

wget https://desktop.docker.com/linux/main/amd64/docker-desktop-amd64.deb?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-linux-amd64

sudo apt-get install ./docker-desktop-amd64.deb

Cassiano · Janeiro 19, 2026, 4:52pm

Error: host and container port ranges have different lengths: 10 vs 1

Da uma olhada no docker-compose.yml o range de portas tem que ser exatamente iguais no podman e no compose.

potentially insufficient UIDs or GIDs available in user namespace
lchown /etc/gshadow: invalid argument

Provavelmente rodando run “podman system migrate” resolva esse erro

Failed to get container status, is Docker installed?
spawn docker ENOENT
Cannot connect to the Docker daemon

O docker esta instalado?

italo.rp · Janeiro 19, 2026, 5:32pm

Não kkkk
Não inicia o daemon e quando inicia, o próximo passo da sempre o mesmo erro. O Winboat fala que houve um erro.

Mais erros que eu possa contar depois dos comandos que você sugeriu rsrs

Aviso: Ocorreu um erro durante a verificação da assinatura. O repositório não é atualizado e os arquivos de índice anteriores serão usados. Verificação de assinatura OpenPGP falhou: https://brave-browser-apt-release.s3.brave.com stable InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Error: Failed to parse keyring “/usr/share/keyrings/brave-browser-archive-keyring.gpg”  Caused by:     0: Reading “/usr/share/keyrings/brave-browser-archive-keyring.gpg”: No such file or directory (os error 2)     1: No such file or directory (os error 2)
Aviso: https://deb.nodesource.com/node_20.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details
Aviso: Falhou ao obter https://brave-browser-apt-release.s3.brave.com/dists/stable/InRelease  Sub-process /usr/bin/sqv returned an error code (1), error message is: Error: Failed to parse keyring “/usr/share/keyrings/brave-browser-archive-keyring.gpg”  Caused by:     0: Reading “/usr/share/keyrings/brave-browser-archive-keyring.gpg”: No such file or directory (os error 2)     1: No such file or directory (os error 2)
Aviso: Falha no download de alguns arquivos de índice. Eles foram ignorados, ou os antigos usados em seu lugar.
user@user:~
$ sudo install -m 0755 -d /etc/apt/keyrings
user@user:~
$ sudo curl -fsSL https://download.docker.com/linux/debian/gpg -o /etc/apt/keyrings/docker.asc
user@user:~
$ sudo chmod a+r /etc/apt/keyrings/docker.asc
user@user:~
$ sudo tee /etc/apt/sources.list.d/docker.sources

user@user:~
$ sudo tee /etc/apt/sources.list.d/docker.sources <<EOF
Types: deb
URIs: 

Suites: $(. /etc/os-release && echo “$VERSION_CODENAME”)
Components: stable
Signed-By: /etc/apt/keyrings/docker.asc
EOF
Types: deb
URIs: 

Suites: trixie
Components: stable
Signed-By: /etc/apt/keyrings/docker.asc
user@user:~
$ sudo apt update
Atingido:1 
 trixie InRelease
Atingido:2 
 trixie-updates InRelease
Atingido:3 
 trixie-security InRelease
Atingido:4 https://linux.teamviewer.com/deb stable InRelease
Atingido:5 https://deb.nodesource.com/node_20.x nodistro InRelease
Atingido:6 
 trixie InRelease
Atingido:7 https://brave-browser-apt-release.s3.brave.com stable InRelease
Erro:7 https://brave-browser-apt-release.s3.brave.com stable InRelease
Sub-process /usr/bin/sqv returned an error code (1), error message is: Error: Failed to parse keyring “/usr/share/keyrings/brave-browser-archive-keyring.gpg”  Caused by:     0: Reading “/usr/share/keyrings/brave-browser-archive-keyring.gpg”: No such file or directory (os error 2)     1: No such file or directory (os error 2)
Atingido:8 https://cid-doc.github.io/pkgs/apt/debian sid InRelease
Atingido:10 https://debrepo.freedownloadmanager.org jammy InRelease
Atingido:9 
 trixie InRelease
Todos os pacotes estão atualizados.
Aviso: https://deb.nodesource.com/node_20.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details
Aviso: O alvo Packages (stable/binary-amd64/Packages) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo Packages (stable/binary-all/Packages) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo Translations (stable/i18n/Translation-pt_BR) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo Translations (stable/i18n/Translation-pt) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo Translations (stable/i18n/Translation-en) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo DEP-11 (stable/dep11/Components-amd64.yml) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo DEP-11 (stable/dep11/Components-all.yml) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo DEP-11-icons-small (stable/dep11/icons-48x48.tar) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo DEP-11-icons (stable/dep11/icons-64x64.tar) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo DEP-11-icons-large (stable/dep11/icons-128x128.tar) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo Contents-deb (stable/Contents-amd64) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo Contents-deb (stable/Contents-all) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Nota: Pulando a aquisição do arquivo configurado ‘stable/binary-i386/Packages’, pois o repositório ‘
 trixie InRelease’ não tem suporte à arquitetura ‘i386’
Aviso: Ocorreu um erro durante a verificação da assinatura. O repositório não é atualizado e os arquivos de índice anteriores serão usados. Verificação de assinatura OpenPGP falhou: https://brave-browser-apt-release.s3.brave.com stable InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Error: Failed to parse keyring “/usr/share/keyrings/brave-browser-archive-keyring.gpg”  Caused by:     0: Reading “/usr/share/keyrings/brave-browser-archive-keyring.gpg”: No such file or directory (os error 2)     1: No such file or directory (os error 2)
Aviso: Falhou ao obter https://brave-browser-apt-release.s3.brave.com/dists/stable/InRelease  Sub-process /usr/bin/sqv returned an error code (1), error message is: Error: Failed to parse keyring “/usr/share/keyrings/brave-browser-archive-keyring.gpg”  Caused by:     0: Reading “/usr/share/keyrings/brave-browser-archive-keyring.gpg”: No such file or directory (os error 2)     1: No such file or directory (os error 2)
Aviso: Falha no download de alguns arquivos de índice. Eles foram ignorados, ou os antigos usados em seu lugar.
Aviso: O alvo Packages (stable/binary-amd64/Packages) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo Packages (stable/binary-all/Packages) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo Translations (stable/i18n/Translation-pt_BR) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo Translations (stable/i18n/Translation-pt) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo Translations (stable/i18n/Translation-en) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo DEP-11 (stable/dep11/Components-amd64.yml) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo DEP-11 (stable/dep11/Components-all.yml) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo DEP-11-icons-small (stable/dep11/icons-48x48.tar) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo DEP-11-icons (stable/dep11/icons-64x64.tar) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo DEP-11-icons-large (stable/dep11/icons-128x128.tar) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo Contents-deb (stable/Contents-amd64) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
Aviso: O alvo Contents-deb (stable/Contents-all) está configurado várias vezes em /etc/apt/sources.list.d/docker.list:1 e /etc/apt/sources.list.d/docker.sources:1
user@user:~
$ sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
docker-ce já é a versão mais nova (5:29.1.5-1~debian.13~trixie).
docker-ce-cli já é a versão mais nova (5:29.1.5-1~debian.13~trixie).
docker-ce-cli configurado para instalar manualmente.
containerd.io já é a versão mais nova (2.2.1-1~debian.13~trixie).
containerd.io configurado para instalar manualmente.
Instalando:
docker-buildx-plugin  docker-compose-plugin

Resumo:
Atualizando: 0, Instalando: 2, Removendo: 0, Não atualizando: 0
Tamanho de download: 24,1 MB
Espaço necessário: 113 MB / 129 GB disponível

Continuar? [S/n]
Obter:1 
 trixie/stable amd64 docker-buildx-plugin amd64 0.30.1-1~debian.13~trixie [16,4 MB]
Obter:2 
 trixie/stable amd64 docker-compose-plugin amd64 5.0.1-1~debian.13~trixie [7.713 kB]
Obtidos 24,1 MB em 7s (3.446 kB/s)
(Lendo banco de dados … 438588 arquivos e diretórios atualmente instalados).
Preparando para desempacotar …/docker-buildx-plugin_0.30.1-1~debian.13~trixie_amd64.deb …
Desempacotando docker-buildx-plugin (0.30.1-1~debian.13~trixie) …
dpkg: erro processando o arquivo /var/cache/apt/archives/docker-buildx-plugin_0.30.1-1~debian.13~trixie_amd64.deb (–unpack):
tentando sobrescrever ‘/usr/libexec/docker/cli-plugins/docker-buildx’, que também está no pacote docker-buildx (0.13.1+ds1-3)
dpkg-deb: erro: o subprocesso colagem foi finalizado por sinal (Pipe quebrado)
Preparando para desempacotar …/docker-compose-plugin_5.0.1-1~debian.13~trixie_amd64.deb …
Desempacotando docker-compose-plugin (5.0.1-1~debian.13~trixie) …
dpkg: erro processando o arquivo /var/cache/apt/archives/docker-compose-plugin_5.0.1-1~debian.13~trixie_amd64.deb (–unpack):
tentando sobrescrever ‘/usr/libexec/docker/cli-plugins/docker-compose’, que também está no pacote docker-compose (2.26.1-4)
dpkg-deb: erro: o subprocesso colagem foi finalizado por sinal (Pipe quebrado)
Erros foram encontrados durante o processamento de:
/var/cache/apt/archives/docker-buildx-plugin_0.30.1-1~debian.13~trixie_amd64.deb
/var/cache/apt/archives/docker-compose-plugin_5.0.1-1~debian.13~trixie_amd64.deb
Erro: Sub-process /usr/bin/dpkg returned an error code (1)
user@user:~
$ sudo apt-get install ./docker-desktop-amd64.deb
Lendo listas de pacotes… Concluído
E: Arquivo sem suporte ./docker-desktop-amd64.deb fornecido na linha de comando
user@user:~
$ sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
docker-ce já é a versão mais nova (5:29.1.5-1~debian.13~trixie).
docker-ce-cli já é a versão mais nova (5:29.1.5-1~debian.13~trixie).
containerd.io já é a versão mais nova (2.2.1-1~debian.13~trixie).
Instalando:
docker-buildx-plugin  docker-compose-plugin

Resumo:
Atualizando: 0, Instalando: 2, Removendo: 0, Não atualizando: 0
Tamanho de download: 0 B / 24,1 MB
Espaço necessário: 113 MB / 129 GB disponível

Continuar? [S/n]
(Lendo banco de dados … 438588 arquivos e diretórios atualmente instalados).
Preparando para desempacotar …/docker-buildx-plugin_0.30.1-1~debian.13~trixie_amd64.deb …
Desempacotando docker-buildx-plugin (0.30.1-1~debian.13~trixie) …
dpkg: erro processando o arquivo /var/cache/apt/archives/docker-buildx-plugin_0.30.1-1~debian.13~trixie_amd64.deb (–unpack):
tentando sobrescrever ‘/usr/libexec/docker/cli-plugins/docker-buildx’, que também está no pacote docker-buildx (0.13.1+ds1-3)
dpkg-deb: erro: o subprocesso colagem foi finalizado por sinal (Pipe quebrado)
Preparando para desempacotar …/docker-compose-plugin_5.0.1-1~debian.13~trixie_amd64.deb …
Desempacotando docker-compose-plugin (5.0.1-1~debian.13~trixie) …
dpkg: erro processando o arquivo /var/cache/apt/archives/docker-compose-plugin_5.0.1-1~debian.13~trixie_amd64.deb (–unpack):
tentando sobrescrever ‘/usr/libexec/docker/cli-plugins/docker-compose’, que também está no pacote docker-compose (2.26.1-4)
dpkg-deb: erro: o subprocesso colagem foi finalizado por sinal (Pipe quebrado)
Erros foram encontrados durante o processamento de:
/var/cache/apt/archives/docker-buildx-plugin_0.30.1-1~debian.13~trixie_amd64.deb
/var/cache/apt/archives/docker-compose-plugin_5.0.1-1~debian.13~trixie_amd64.deb
Erro: Sub-process /usr/bin/dpkg returned an error code (1)

italo.rp · Janeiro 19, 2026, 5:33pm

Cara. Já que está me ajudando. Então me ajuda em uma ideia aqui.

O que preciso fazer para limpar tudo? Começar docker e podman do zero e limpar esses erros?

Faço isso e a gente começa do zero passo a passo e vê no que eu tô errando.

LinuxUser · Janeiro 19, 2026, 5:45pm

Qual a versão do MX Linux você está usando? Vou tentar replicar o erro.

LinuxUser · Janeiro 19, 2026, 5:47pm

Aliás, o comando está escrito errado nessa entrada. Tenta copiar o que eu coloquei no comentário anterior e executar denovo para ver o resultado.

italo.rp · Janeiro 19, 2026, 6:14pm

italo.rp · Janeiro 19, 2026, 6:15pm

run “podman system migrate” apenas roda, mas não acontece nada e também não sana o erro. Já tentei várias vezes.

Docker está instalado, instalei por algumas vias, inclusive via LinuxToys

LinuxUser · Janeiro 19, 2026, 6:36pm

Corta aquela parte em que aparece seu IP para não expor a localização.

LinuxUser · Janeiro 19, 2026, 6:37pm

Talvez o problema esteja ocorrendo porque você instalou pelo LinuxToys. Desinstala o Docker e depois instale novamente seguindo o passo-a-passo que eu postei.

italo.rp · Janeiro 19, 2026, 6:41pm

Nem notei. Obrigado.

italo.rp · Janeiro 19, 2026, 6:49pm

sudo apt update
Atingido:1 http://deb.debian.org/debian trixie InRelease
Atingido:2 http://security.debian.org/debian-security trixie-security InRelease
Atingido:3 https://linux.teamviewer.com/deb stable InRelease
Atingido:4 https://cid-doc.github.io/pkgs/apt/debian sid InRelease
Atingido:5 https://brave-browser-apt-release.s3.brave.com stable InRelease
Atingido:6 https://deb.nodesource.com/node_20.x nodistro InRelease
Atingido:7 http://deb.debian.org/debian trixie-updates InRelease
Atingido:9 https://debrepo.freedownloadmanager.org jammy InRelease
Atingido:8 https://mxrepo.com/mx/repo trixie InRelease
Todos os pacotes estão atualizados.

Tudo certo com o update. Gerou alguns erros de pacote obsoletos/conflitantes de algumas outras soluções que tentei, tipo o nodejs que acabei instalando para resolver alguns problemas do docker e algumas outras coisas que eu estava tentando.

Update deu bom. Agora vou começar tudo do zero seguindo a doc na Docker.

italo.rp · Janeiro 19, 2026, 7:02pm

Docker devidamente instalado. Porém daemon não inicia.

Segui a doc para iniciar o daemon, mas o comando não tem sáida, não sei se é padrão, mas não starta o daemon.