Instead of using sudo systemctl start docker use: sudo /etc/init.d/docker start , as of right now we do not have systemd in WSL 2.
That is, there is no systemd command in wsl2, so we need to use sudo /etc/init.d/docker start instead sudo systemctl start docker
Read More:
- [Solved] docker Error: System has not been booted with systemd as init system (PID 1). Can‘t operate. Failed to con
- See system logs and ‘systemctl status docker.service‘ for details
- [Solved] Warning: detected “cgroupfs“ as the Docker cgroup driver. The recommended driver is “systemd“.
- [Solved] Error: ENOSPC: System limit for number of file watchers reached
- Linux Install Docker Error: Failed to restart docker.service: Unit docker.service not found.
- [Solved] Linux Error: ENOSPC: System limit for number of file watchers
- redhat7. 5 system service is not started automatically and use systemctl start error: error getting authority: error initializing authority: CO, (the server will restart)
- ERROR: This system does not support “RDRAND“ [How to Solve]
- Prompt “entering emergency mode. Exit the shell to continue” if the Linux operating system does not start normally
- [Solved] Linux virtual machine startup error: operating system not found
- How to Solve Xmind Install Error in Ubuntu System
- [Solved] failed to start remount root and kernel file system
- [Solved] Docker error: “unknown runtime specified NVIDIA” using GPU“
- [Solved] kubeadm join Cluster Error: error execution phase kubelet-start
- Linux system service command error: Failed to allocate directory watch: Too many open files
- [Solved] RHEL 7 installs Oracle RAC 11.2.0.4, executes root.sh error ohasd: failed to start
- [Solved] Linux Error: Error: ENOSPC: System limit for number of file watchers
- cstdio [Error] ‘::fpos_t‘ has not been declared [How to Solve]
- Linux: How to Solve sudo operate Error
- [Solved] NVIDIA-SMI has failed because it couldn‘t communicate with the NVIDIA driver.