Hello,
I started using Linux a few months ago when I got a Jeton Nano for a Masters Course Project. I’ve had this issue with the jeston for about a week now, I’ve been searching for solutions, but none seem to work or address directly my issue. I’ll describe the problem and all the error messages i’ve obtained while trying to implement the solutions:
I tried to pull a docker using the following command:
sudo docker pull nvcr.io/nvidia/l4t-ml:r32.5.0-py3
It got installed properly, and no problema was shown, however just after I rebooted and connected to the jeston via SSH, I tried running the container using:
“sudo docker run -it --rm --runtime nvidia --network host nvcr.io/nvidia/l4t-ml:r32.5.0-py3”
“The following error message appeared: docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is he docker daemon running?.”
After used the following two commands I found on a blog:
“sudo systemctl unmask docker”
“systemctl start docker”
The latter caused this error message:
“Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.ShuttingDown: Refusing activation, D-Bus is shutting down. (g-io-error-quark, 36)
Failed to start docker.service: Refusing activation, D-Bus is shutting down.
See system logs and ‘systemctl status docker.service’ for details.”
Then runned:
“systemctl status docker”
docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset:
Active: failed (Result: exit-code) since Fri 2021-04-30 20:05:46 -05; 13min
Docs: https://docs.docker.com
Main PID: 9805 (code=exited, status=1/FAILURE)
abr 30 20:05:46 linux systemd[1]: docker.service: Service hold-off time over, s
abr 30 20:05:46 linux systemd[1]: docker.service: Scheduled restart job, restar
abr 30 20:05:46 linux systemd[1]: Stopped Docker Application Container Engine.
abr 30 20:05:46 linux systemd[1]: docker.service: Start request repeated too qu
abr 30 20:05:46 linux systemd[1]: docker.service: Failed with result 'exit-code
abr 30 20:05:46 linux systemd[1]: Failed to start Docker Application Container
After searching more, I found I should restart Daemon, so I ran the following line:
“sudo dockerd”
I got the following error message:
"" INFO[2021-04-30T20:22:44.923076495-05:00] Starting up
INFO[2021-04-30T20:22:44.924775415-05:00] detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf
INFO[2021-04-30T20:22:44.925994592-05:00] parsed scheme: “unix” module=grpc
INFO[2021-04-30T20:22:44.926047614-05:00] scheme “unix” not registered, fallback to default scheme module=grpc
INFO[2021-04-30T20:22:44.926115427-05:00] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 }] } module=grpc
INFO[2021-04-30T20:22:44.926153239-05:00] ClientConn switching balancer to “pick_first” module=grpc
INFO[2021-04-30T20:22:44.928441019-05:00] parsed scheme: “unix” module=grpc
INFO[2021-04-30T20:22:44.928512218-05:00] scheme “unix” not registered, fallback to default scheme module=grpc
INFO[2021-04-30T20:22:44.928567427-05:00] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 }] } module=grpc
INFO[2021-04-30T20:22:44.928613104-05:00] ClientConn switching balancer to “pick_first” module=grpc
ERRO[2021-04-30T20:22:44.956576882-05:00] [graphdriver] prior storage driver overlay2 failed: lstat /var/lib/docker/overlay2/8d229224131676e6d0de1fce670d658a47467cbffeca0a401ee0cac0f1037634: structure needs cleaning
failed to start daemon: error initializing graphdriver: lstat /var/lib/docker/overlay2/8d229224131676e6d0de1fce670d658a47467cbffeca0a401ee0cac0f1037634: structure needs cleaning “”.
I would appreciate any help. And sorry if I make any mistake on the post, it’s my first time posting on any of these platforms. Thanks