From the comments, it sounded like this may be due to a bug of some sort in the Preview version of WSL installed from the Store.
Ultimately (also from the comments), the problem turned out to be that one of the Docker WSL instances became the "default" for WSL. So running the "Debian" distribution specifically would work. Running the WSL application (which runs wsl.exe),however, was attempting to start the docker image, which isn't meant to be accessed directly (and was resulting in the fstab error).
This was found via wsl -l -v showing the Docker image as default.
The solution was to use:
wsl -s Debian
... to set the default distribution.
While this isn't necessary a "bug", there is an open Github issue suggesting that WSL have a mechanism that will allow docker-desktop-data (and other distributions that aren't supposed to be run by the end-user) to be "hidden".
