docker-swarm | blog series on Docker Swarm example using VirtualBox | Continuous Deployment library

I have an async FastApi application with async sqlalchemy, source code (will not provide schemas.py because it is not necessary):

I'm creating worker_threads in node and I'm collecting them to custom WorkerPool. All workers are unique, because they have unique worker.threadId. My app have ability to terminate specific worker -- I have terminateById() method in WorkerPool.

So if you have one node.js instance -- everything is all right. But if you're trying to use docker-swarm or Kubernetes -- you will have n amount of different WorkerPool instances. So, for example, you have created some workers in one node instance and now you're trying to terminate one -- it means you have some request with threadId(or other unique data to identify worker). For example your load balancer have chosen to use another node instance for this request, in this instance you have no workers.

At first I thought, that I can change unique index for worker to something like userId+ThreadId and then store it in redis for example. But then I haven't found any info about something like Worker.findByThreadID(). Then what can I do in situation, when you have multiple node instances?

UPDATE: I have found some info about sticky sessions in load balancers. That means, that using cookies we can stick specific user to specific node instance, but this in my case this stickiness has to be active until worker is terminated. It can last for days

Section 1

I am trying to execute "exec" on one of the containers in a stack or service. I have followed the answers provided here execute a command within docker swarm service as well as on the official Docker documentation here https://docs.docker.com/engine/swarm/secrets/ but it seems "docker container list" and its variants ("docker ps") seem not to find any container listed in the "docker service list".

See the example below from https://docs.docker.com/engine/swarm/secrets/ which is meant to use of "exec" on a container of a service.

1)

I'm running gitlab-ce on-prem with min.io as a local S3 service. CI/CD caching is working, and basic connectivity with the S3-compatible minio is good. (Versions: gitlab-ce:13.9.2-ce.0, gitlab-runner:v13.9.0, and minio/minio:latest currently c253244b6fb0.)

Is there additional configuration to differentiate between job-artifacts and pipeline-artifacts and storing them in on-prem S3-compatible object storage?

In my test repo, the "build" stage builds a sparse R package. When I was using local in-gitlab job artifacts, it succeeds and moves on to the "test" and "deploy" stages, no problems. (And that works with S3-stored cache, though that configuration is solely within gitlab-runner.) Now that I've configured minio as a local S3-compatible object storage for artifacts, though, it fails.

I am trying to get a very simple docker-swarm going. If I start the container using docker-compose up -d I am able to go to locahost and see the 'Hello message'. Running docker stack deploy -c docker-compose.yml swar starts the swarm fine. docker ps

docker service ls

However navigating to localhost, 0.0.0.0, 127.0.0.1 or IP of machine doesn't work, it just timesout with 'This site can't be reached. took too long to respond.' Ive also tried it with another small tutorial from github, which also has same issue. Any ideas what is wrong?

server.js:

Set up two servers, one as a manager node and one as a worker node.

The worker node is labeled role_1=true .

The manager node is labeled role_2, role_3.

I have a Jenkins Job DSL job that worked well until about january (it is not used that often). Last week, the job failed with the error message ERROR: java.io.IOException: Failed to persist config.xml (no Stack trace, just that message). There were no changes to the job since the last successful execution in january.

I am using fabric 2.2 version and working on docker-machine. when i try to create channel by using peer channel create method through CLI, i got this error.

Error: got unexpected status: BAD_REQUEST -- error validating channel creation transaction for new channel 'mychannel', could not successfully apply update to template configuration: error authorizing update: error validating DeltaSet: policy for [Group] /Channel/Application not satisfied: implicit policy evaluation failed 0 sub-policies were satisfied, but this policy requires 1 of the 'Admins' sub-policies to be satisfied

code:

I'm getting the following error when trying to login using root and the initial password set using the Install GitLab using Docker swarm mode method. Any suggestions how how to resolve this? The error is a 401 Unauthorized, but as you can see below the root does get created with the supplied password file.