boot2docker | DEPRECATED ; see https | Continuous Deployment library

As per the Docker documentation, overlay network is automatically getting created when we initialise docker swarm. But we can not use that network for individual docker container which not part of swarm resource. So, we need to create overlay network with "--attachable" flag.

I tried to create attachable overlay network but I am getting following error :

I was following the documentation here to build hono from source code - [1]: https://www.eclipse.org/hono/docs/dev-guide/building_hono/

But the build fails with this error -

[ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.33.0:build (build_images) on project hono-adapter-amqp-vertx: Cannot create docker access object : extension (5) should not be presented in certificate_request -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal io.fabric8:docker-maven-plugin:0.33.0:build (build_images) on project hono-adapter-amqp-vertx: Cannot create docker access object

The docker client version installed in my machine is 19.03.1 and server version is 19.03.02 java version is 11.0.7

The detailed dump with X option is here - [2]: https://docdro.id/AMRsFem

Please let know how to fix this.

Updated with more info

$ docker info Client: Debug Mode: false

Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 19.03.12 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk >syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429 runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd init version: fec3683 Security Options: seccomp Profile: default Kernel Version: 4.19.130-boot2docker Operating System: Boot2Docker 19.03.12 (TCL 10.1) OSType: linux Architecture: x86_64 CPUs: 1 Total Memory: 985.4MiB Name: default ID: JGCF:FKDA:TRZS:L3E3:U5FP:PUTI:VTXZ:M2TN:PITL:P74X:AMJJ:YRPO Docker Root Dir: /mnt/sda1/var/lib/docker Debug Mode: false No Proxy: 192.168.99.100 Registry: https://index.docker.io/v1/ Labels: provider=virtualbox Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false Product License: Community Engine

$ echo $DOCKER_HOST >tcp://192.168.99.108:2376

Command used to build -

mvn clean install -Ddocker.host=tcp://192.168.99.108:2376 -Pbuild-docker-image,metrics-prometheus

Docker toolbox installed for windows 10 Home Edition. Docker toolbox for this OS is installed. But when I can start learning the program, it gives me these errors. I cannot create an image or run an image. At the end of each error message it tells me that I have a server misbehaving. At the moment of running an image gives me the following error:

Docker says it is running, but it clearly isn't.

Machine is OSX 10.15.4

I am following this tutorial to run Kafka inside a Docker container on windows.

When I try to launch Kafka-Manager by opening http://localhost:9000 in the browser as described there, I get ERR_CONNECTION_REFUSED.

Something I think might be related is that at the first time I ran docker-compose up, PowerShell showed an error saying I needed to run some command first, to open a virtual machine or something like that.

Then I ran the command that PowerShell had told me and then I managed to run docker-compose up successfully. However the tutorial didn't mention anything about it, and since then every time I tried to run docker-compose up I managed to to it without running another command first, even if I closed and reopened PowerShell.

I suspect PowerShell remembers I'm connected to a virtual machine so docker-compose up runs Kafka inside a virtual machine, and therefore I can't reach Kafka-Manager in the browser, although I see shows the following message:

kafkamanager | [info] p.c.s.NettyServer - Listening for HTTP on /0.0.0.0:9000

Edit:

docker logs for kafka container:

Scenario: I want to start both Mongo and Mongo-Express from same docker-compose.

I have no issue starting only mongodb from docker-compose. The issue raises when I try to link Mongo-Express to Mongo DB Service.

I am not sure if I am missing either some configuration in docker-compose or in my mongo-express settup. I am not expecting the issue being part of Mongo settup. BTW, I pasted bellow whole docker-compose and and its output.

From bellow logs I can see there is no issue raising Mongo. There is some issue when mongo-express tries connect to Mongo service probably because I didn't settup link properly. On top of that, my Spring Webflux is connecting succesfully to Mongo DB with bellow propertis. The issue is really limited to mongo-express reaching mongodb.

application.yml that allows Spring Data (spring-boot-starter-data-mongodb-reactive) connects successfuly to such MongoDb

I am totally new to docker and recently I follow "The Docker Book" from James to learn about docker by myself. The OS I am using is OSX. The tool I am using to run docker is Docker Desktop for Mac (BTW, Is that a docker-toolbox I am using?).

When I follow the book to run the following code: