Tagged: docker issues
- This topic has 4 replies, 3 voices, and was last updated Dec 30-6:51 pm by eyekay234.
-
AuthorPosts
-
December 22, 2022 at 12:44 am #96039Member
eyekay234
Hello
i have tried installing docker on my system and running into issues. i tried following the instructions found here: https://docs.docker.com/engine/install/debian/ but dokcer doesnt run.
even after running the following below this is what displays:
sudo service docker start
sudo docker run hello-world
Starting Docker: docker.
docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
See ‘docker run –help’.December 22, 2022 at 9:15 am #96042MemberRobin
::try
sudo dockerdWindows is like a submarine. Open a window and serious problems will start.
December 22, 2022 at 11:13 am #96047MemberPPC
::Since I’ve been curious about docker for a long time, I installed it and tried to run the commands from the OP (I got the same result), then “sudo dockerd”. I got this:
$ sudo dockerd INFO[2022-12-22T11:09:59.431871340Z] libcontainerd: docker-containerd is still running pid=7164 INFO[2022-12-22T11:09:59.431973000Z] parsed scheme: "unix" module=grpc INFO[2022-12-22T11:09:59.431985423Z] scheme "unix" not registered, fallback to default scheme module=grpc INFO[2022-12-22T11:09:59.432019466Z] ccResolverWrapper: sending new addresses to cc: [{unix:///var/run/docker/containerd/containerd.sock 0 <nil>}] module=grpc INFO[2022-12-22T11:09:59.432039825Z] ClientConn switching balancer to "pick_first" module=grpc INFO[2022-12-22T11:09:59.432078200Z] pickfirstBalancer: HandleSubConnStateChange: 0xc0005df5d0, CONNECTING module=grpc ERRO[2022-12-22T11:10:09.432195718Z] failed connecting to containerd error="failed to dial \"/var/run/docker/containerd/containerd.sock\": context deadline exceeded" module=libcontainerd INFO[2022-12-22T11:10:09.532525803Z] killing and restarting containerd module=libcontainerd pid=7164 panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x556b33808930] goroutine 21 [running]: github.com/containerd/containerd.(*Client).Close(0x0, 0x0, 0x0) /build/docker.io-sMo5uP/docker.io-18.09.1+dfsg1/.gopath/src/github.com/containerd/containerd/client.go:536 +0x30 github.com/docker/docker/libcontainerd/supervisor.(*remote).monitorDaemon(0xc0006101a0, 0x556b349c9f80, 0xc000629b00) /build/docker.io-sMo5uP/docker.io-18.09.1+dfsg1/.gopath/src/github.com/docker/docker/libcontainerd/supervisor/remote_daemon.go:321 +0x24f created by github.com/docker/docker/libcontainerd/supervisor.Start /build/docker.io-sMo5uP/docker.io-18.09.1+dfsg1/.gopath/src/github.com/docker/docker/libcontainerd/supervisor/remote_daemon.go:90 +0x3b5After that, if I try to run again, I get the same result:
$ sudo docker run hello-world docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. See 'docker run --help'.P.
December 22, 2022 at 11:39 am #96048MemberPPC
::Solution:
1- check if the service is running (it seems it starts automatically, once installed):
service docker status [ ok ] Docker is running.2- Stop the service:
sudo service docker stop [ ok ] Stopping Docker: docker.3- Start dockerd:
sudo dockerd &Then you can run any docker instance you want:
sudo docker run hello-world Unable to find image 'hello-world:latest' locally latest: Pulling from library/hello-world 2db29710123e: Pull complete Digest: sha256:c77be1d3a47d0caf71a82dd893ee61ce01f32fc758031a6ec4cf1389248bb833 Status: Downloaded newer image for hello-world:latest Hello from Docker! This message shows that your installation appears to be working correctly. To generate this message, Docker took the following steps: 1. The Docker client contacted the Docker daemon. 2. The Docker daemon pulled the "hello-world" image from the Docker Hub. (amd64) 3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading. 4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal. To try something more ambitious, you can run an Ubuntu container with: $ docker run -it ubuntu bash Share images, automate workflows, and more with a free Docker ID: https://hub.docker.com/ For more examples and ideas, visit: https://docs.docker.com/get-started/December 30, 2022 at 6:51 pm #96453Member
eyekay234
::@ppc
i tried on my own system and this is the result of what i got below:
$ sudo dockerd
INFO[2022-12-30T19:49:01.042429906+01:00] Starting up
INFO[2022-12-30T19:49:01.043853018+01:00] libcontainerd: started new containerd process pid=476
INFO[2022-12-30T19:49:01.043916216+01:00] parsed scheme: “unix” module=grpc
INFO[2022-12-30T19:49:01.043936624+01:00] scheme “unix” not registered, fallback to default scheme module=grpc
INFO[2022-12-30T19:49:01.043995646+01:00] ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock <nil> 0 <nil>}] <nil> <nil>} module=grpc
INFO[2022-12-30T19:49:01.044022721+01:00] ClientConn switching balancer to “pick_first” module=grpc
WARN[0000] containerd config version1has been deprecated and will be removed in containerd v2.0, please switch to version2, see https://github.com/containerd/containerd/blob/main/docs/PLUGINS.md#version-header
INFO[2022-12-30T19:49:01.081568073+01:00] starting containerd revision=9ba4b250366a5ddde94bb7c9d1def331423aa323 version=1.6.14
INFO[2022-12-30T19:49:01.099241196+01:00] loading plugin “io.containerd.content.v1.content”… type=io.containerd.content.v1
INFO[2022-12-30T19:49:01.099370027+01:00] loading plugin “io.containerd.snapshotter.v1.aufs”… type=io.containerd.snapshotter.v1
INFO[2022-12-30T19:49:01.114174308+01:00] skip loading plugin “io.containerd.snapshotter.v1.aufs”… error=”aufs is not supported (modprobe aufs failed: exit status 1 \”modprobe: FATAL: Module aufs not found in directory /lib/modules/5.10.142-antix.2-amd64-smp\\n\”): skip plugin” type=io.containerd.snapshotter.v1
INFO[2022-12-30T19:49:01.114229695+01:00] loading plugin “io.containerd.snapshotter.v1.btrfs”… type=io.containerd.snapshotter.v1
INFO[2022-12-30T19:49:01.114422403+01:00] skip loading plugin “io.containerd.snapshotter.v1.btrfs”… error=”path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs (ext4) must be a btrfs filesystem to be used with the btrfs snapshotter: skip plugin” type=io.containerd.snapshotter.v1
INFO[2022-12-30T19:49:01.114447685+01:00] loading plugin “io.containerd.snapshotter.v1.devmapper”… type=io.containerd.snapshotter.v1
WARN[2022-12-30T19:49:01.114481001+01:00] failed to load plugin io.containerd.snapshotter.v1.devmapper error=”devmapper not configured”
INFO[2022-12-30T19:49:01.114504844+01:00] loading plugin “io.containerd.snapshotter.v1.native”… type=io.containerd.snapshotter.v1
INFO[2022-12-30T19:49:01.114554585+01:00] loading plugin “io.containerd.snapshotter.v1.overlayfs”… type=io.containerd.snapshotter.v1
INFO[2022-12-30T19:49:01.114690934+01:00] loading plugin “io.containerd.snapshotter.v1.zfs”… type=io.containerd.snapshotter.v1
INFO[2022-12-30T19:49:01.114840889+01:00] skip loading plugin “io.containerd.snapshotter.v1.zfs”… error=”path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter: skip plugin” type=io.containerd.snapshotter.v1
INFO[2022-12-30T19:49:01.114864050+01:00] loading plugin “io.containerd.metadata.v1.bolt”… type=io.containerd.metadata.v1
WARN[2022-12-30T19:49:01.114901138+01:00] could not use snapshotter devmapper in metadata plugin error=”devmapper not configured”
INFO[2022-12-30T19:49:01.114922129+01:00] metadata content store policy set policy=shared
INFO[2022-12-30T19:49:01.115053202+01:00] loading plugin “io.containerd.differ.v1.walking”… type=io.containerd.differ.v1
INFO[2022-12-30T19:49:01.115084964+01:00] loading plugin “io.containerd.event.v1.exchange”… type=io.containerd.event.v1
INFO[2022-12-30T19:49:01.115115262+01:00] loading plugin “io.containerd.gc.v1.scheduler”… type=io.containerd.gc.v1
INFO[2022-12-30T19:49:01.115160285+01:00] loading plugin “io.containerd.service.v1.introspection-service”… type=io.containerd.service.v1
INFO[2022-12-30T19:49:01.115186928+01:00] loading plugin “io.containerd.service.v1.containers-service”… type=io.containerd.service.v1
INFO[2022-12-30T19:49:01.115210782+01:00] loading plugin “io.containerd.service.v1.content-service”… type=io.containerd.service.v1
INFO[2022-12-30T19:49:01.115242492+01:00] loading plugin “io.containerd.service.v1.diff-service”… type=io.containerd.service.v1
INFO[2022-12-30T19:49:01.115275834+01:00] loading plugin “io.containerd.service.v1.images-service”… type=io.containerd.service.v1
INFO[2022-12-30T19:49:01.115301375+01:00] loading plugin “io.containerd.service.v1.leases-service”… type=io.containerd.service.v1
INFO[2022-12-30T19:49:01.115335330+01:00] loading plugin “io.containerd.service.v1.namespaces-service”… type=io.containerd.service.v1
INFO[2022-12-30T19:49:01.115362212+01:00] loading plugin “io.containerd.service.v1.snapshots-service”… type=io.containerd.service.v1
INFO[2022-12-30T19:49:01.115392064+01:00] loading plugin “io.containerd.runtime.v1.linux”… type=io.containerd.runtime.v1
INFO[2022-12-30T19:49:01.115470879+01:00] loading plugin “io.containerd.runtime.v2.task”… type=io.containerd.runtime.v2
INFO[2022-12-30T19:49:01.115521951+01:00] loading plugin “io.containerd.monitor.v1.cgroups”… type=io.containerd.monitor.v1
INFO[2022-12-30T19:49:01.115964294+01:00] loading plugin “io.containerd.service.v1.tasks-service”… type=io.containerd.service.v1
INFO[2022-12-30T19:49:01.116045412+01:00] loading plugin “io.containerd.grpc.v1.introspection”… type=io.containerd.grpc.v1
INFO[2022-12-30T19:49:01.116080048+01:00] loading plugin “io.containerd.internal.v1.restart”… type=io.containerd.internal.v1
INFO[2022-12-30T19:49:01.116173612+01:00] loading plugin “io.containerd.grpc.v1.containers”… type=io.containerd.grpc.v1
INFO[2022-12-30T19:49:01.116207453+01:00] loading plugin “io.containerd.grpc.v1.content”… type=io.containerd.grpc.v1
INFO[2022-12-30T19:49:01.116238954+01:00] loading plugin “io.containerd.grpc.v1.diff”… type=io.containerd.grpc.v1
INFO[2022-12-30T19:49:01.116268630+01:00] loading plugin “io.containerd.grpc.v1.events”… type=io.containerd.grpc.v1
INFO[2022-12-30T19:49:01.116298447+01:00] loading plugin “io.containerd.grpc.v1.healthcheck”… type=io.containerd.grpc.v1
INFO[2022-12-30T19:49:01.116327313+01:00] loading plugin “io.containerd.grpc.v1.images”… type=io.containerd.grpc.v1
INFO[2022-12-30T19:49:01.116355626+01:00] loading plugin “io.containerd.grpc.v1.leases”… type=io.containerd.grpc.v1
INFO[2022-12-30T19:49:01.116387248+01:00] loading plugin “io.containerd.grpc.v1.namespaces”… type=io.containerd.grpc.v1
INFO[2022-12-30T19:49:01.116416702+01:00] loading plugin “io.containerd.internal.v1.opt”… type=io.containerd.internal.v1
INFO[2022-12-30T19:49:01.116491338+01:00] loading plugin “io.containerd.grpc.v1.snapshots”… type=io.containerd.grpc.v1
INFO[2022-12-30T19:49:01.116519391+01:00] loading plugin “io.containerd.grpc.v1.tasks”… type=io.containerd.grpc.v1
INFO[2022-12-30T19:49:01.116548619+01:00] loading plugin “io.containerd.grpc.v1.version”… type=io.containerd.grpc.v1
INFO[2022-12-30T19:49:01.116576041+01:00] loading plugin “io.containerd.tracing.processor.v1.otlp”… type=io.containerd.tracing.processor.v1
INFO[2022-12-30T19:49:01.116607824+01:00] skip loading plugin “io.containerd.tracing.processor.v1.otlp”… error=”no OpenTelemetry endpoint: skip plugin” type=io.containerd.tracing.processor.v1
INFO[2022-12-30T19:49:01.116630850+01:00] loading plugin “io.containerd.internal.v1.tracing”… type=io.containerd.internal.v1
ERRO[2022-12-30T19:49:01.116661876+01:00] failed to initialize a tracing processor “otlp” error=”no OpenTelemetry endpoint: skip plugin”
INFO[2022-12-30T19:49:01.117040342+01:00] serving… address=/var/run/docker/containerd/containerd-debug.sock
INFO[2022-12-30T19:49:01.117133402+01:00] serving… address=/var/run/docker/containerd/containerd.sock.ttrpc
INFO[2022-12-30T19:49:01.117209077+01:00] serving… address=/var/run/docker/containerd/containerd.sock
INFO[2022-12-30T19:49:01.117247281+01:00] containerd successfully booted in 0.036489s
INFO[2022-12-30T19:49:01.128456538+01:00] parsed scheme: “unix” module=grpc
INFO[2022-12-30T19:49:01.128486661+01:00] scheme “unix” not registered, fallback to default scheme module=grpc
INFO[2022-12-30T19:49:01.128506278+01:00] ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock <nil> 0 <nil>}] <nil> <nil>} module=grpc
INFO[2022-12-30T19:49:01.128528511+01:00] ClientConn switching balancer to “pick_first” module=grpc
INFO[2022-12-30T19:49:01.132342761+01:00] parsed scheme: “unix” module=grpc
INFO[2022-12-30T19:49:01.132385397+01:00] scheme “unix” not registered, fallback to default scheme module=grpc
INFO[2022-12-30T19:49:01.132423258+01:00] ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock <nil> 0 <nil>}] <nil> <nil>} module=grpc
INFO[2022-12-30T19:49:01.132443094+01:00] ClientConn switching balancer to “pick_first” module=grpc
INFO[2022-12-30T19:49:01.453008724+01:00] [graphdriver] using prior storage driver: overlay2
WARN[2022-12-30T19:49:01.701541359+01:00] Your kernel does not support cgroup blkio weight
WARN[2022-12-30T19:49:01.701573682+01:00] Your kernel does not support cgroup blkio weight_device
INFO[2022-12-30T19:49:01.701725961+01:00] Loading containers: start.
WARN[2022-12-30T19:49:01.704916778+01:00] Running modprobe bridge br_netfilter failed with message: modprobe: ERROR: could not insert ‘bridge’: Exec format error
modprobe: ERROR: could not insert ‘br_netfilter’: Invalid argument
insmod /lib/modules/5.10.142-antix.2-amd64-smp/kernel/net/bridge/bridge.ko
insmod /lib/modules/5.10.142-antix.2-amd64-smp/kernel/net/bridge/br_netfilter.ko
, error: exit status 1
INFO[2022-12-30T19:49:01.741995982+01:00] Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option –bip can be used to set a preferred IP address
INFO[2022-12-30T19:49:01.746279796+01:00] stopping event stream following graceful shutdown error=”<nil>” module=libcontainerd namespace=moby
INFO[2022-12-30T19:49:01.747231936+01:00] stopping event stream following graceful shutdown error=”context canceled” module=libcontainerd namespace=plugins.moby
INFO[2022-12-30T19:49:01.747286047+01:00] stopping healthcheck following graceful shutdown module=libcontainerd
failed to start daemon: Error initializing network controller: Error creating default “bridge” network: package not installedThen i run dpkg -l bridge-utils iptables and get the following below:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-===================================================
ii bridge-utils 1.7-1 amd64 Utilities for configuring the Linux Ethernet bridge
ii iptables 1.8.7-1 amd64 administration tools for packet filtering and NATThen i now run sudo apt-get update && sudo apt-get install bridge-utils iptables and get the following:
Reading package lists… Done
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
bridge-utils is already the newest version (1.7-1).
iptables is already the newest version (1.8.7-1).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.- This reply was modified 4 months, 1 week ago by eyekay234.
-
AuthorPosts
- You must be logged in to reply to this topic.