Isn’t it linked to the use of this : <property> <name>dfs.client.use.datanode.hostname</name> <value>true</value> </property> Using the hostname means being bound to the container and not the service itself, if I’m correct.
Adding health check to the Dockerfile, will make the health-check part of the image, so that anyone pulling the image from the registry will get the health check by default. Compose files are usually less shared than the actual docker images they run. The dockercompose health-check allows adding/overrriding healthchecks for images for someone who is … Read more
Although the ping operation from @nitrin0 answer generally works. It does not handle the case where the write operation will actually fail. So instead I perform a change that will just increment a value to a key I don’t plan to use. image: redis:6 healthcheck: test: [ “CMD”, “redis-cli”, “–raw”, “incr”, “ping” ]
Using composer Since composer v3.2 it is possible to configure the attachable property through the composer file using the keyword attachable like: networks: mynet1: driver: overlay attachable: true Using docker network create Since Docker Engine API v1.25 it is possible to create a network and make it attachable using the –attachable parameter like: docker network … Read more
I’ve had a fair amount of experience with microservices and local development and here’s been some approaches I’ve seen: Run all the things locally on docker or k8. If using k8, then a tool like skaffolding can make it easier to run and debug a service locally in the IDE but put it into your … Read more
Restarting docker worked for me.
There are lots of articles out there which will explain the differences. In a nutshell: Both are trying to solve the same problem – container orchestration over a large number of hosts. Essentially these problems can be broken down like so: Scheduling containers across multiple hosts (taking into account resource utilization etc) Grouping containers into … Read more
Already found the solution. My image is hosted on a private repository. Besides the swarm manager (where I executed the commands), I had a running swarm worker. When I ran docker stack deploy -c docker-compose.yml myapp docker deployed the service to the worker node (not the manager node as I thought). At the worker node, … Read more
Going by question title, and if one doesn’t want to create docker image but just want to run a script using standard python docker images, it can run using below command docker run -it –rm –name my-running-script -v “$PWD”:/usr/src/myapp -w /usr/src/myapp python:3.7-alpine python script_to_run.py
The problem is that your tasks (calling bin/bash) exits quickly since it’s not doing anything. If you look at the tasks for your service, you’ll see that one is started and then shutdown within seconds. Another one is then started, shutdown and so on, since you’re requested that 1 task be running at all times. … Read more