Fydetab Duo WiFi and Linux System Issues

Fydetab Duo
,
1

:pushpin:Question Description

  • Description:
    Currently I’ve installed some docker containers in the Linux subsystem. Basically Nextcloud. After installing the containers, Linux terminal does not open any longer. It keeps restarting to a point where after 10 seconds (more or less) the whole tablet reboots. And since I’ve also installed a tailscale client in the VM, I’ve kept the tablet open for a whole day. I’ve also noticed that after around 12-13 hours of time the tablet has been on (I’ve turned off the sleep settings), the WiFi does not work anymore. It can scan the network, but I cannot connect to any of them.

:computer:System & Device Information

  • Hardware & System Configuration:
    • Fydetab Duo
    • FydeOS v22.1:

How I get past these issues with temporary fixes

  • Linux Subsystem
    • I open up crosh and stop the VM instance:

      vmc stop termina

    • Manually start the VM using explicit Crostini flags:

      vmc start termina --vm-type CROSTINI

    • Then:

      lxc start penguin

In this way, the VM STILL does not open, but my server is accessible through the network.

  • WiFi Issue
    • This one happened every time I kept the tablet on, and I couldn’t find any way to restore the connection rather than restarting it.
2

Hi, thanks for the report. A few suggestions:

About Docker in the Linux subsystem

We don’t recommend running Docker inside the Linux subsystem (Crostini) — it’s nested containerization (Docker inside a container inside a VM), and it’s not very stable.

A full Nextcloud stack (database + PHP + cache) is also a heavy workload for this device, especially on memory. It can drive the system into out-of-memory situations and cause the reboots you’re seeing. If you want to keep running it, please limit your containers’ memory and storage, e.g. in docker-compose.yml:

services:
  db:
    mem_limit: 512m
  app:
    mem_limit: 1g
  redis:
    mem_limit: 128m

Manually starting termina isn’t a full recovery: the Terminal app depends on Chrome’s own startup flow to complete its session handshake with the container, which is why your services come back but the Terminal stays broken. We’d advise against driving termina/Crostini by hand unless you’re very experienced with Linux — it’s easy to break the system that way.

About the WiFi issue

Try it without installing the docker containers, if it still happens, please submit a feedback report, describe the issue briefly, and submit — then paste the report ID here so we can pull the logs on our side.

Thanks!