swarmkit VS Docker Compose

So the thing is support for Swarm was delegated to Mirantis, https://www.mirantis.com/blog/mirantis-will-continue-to-support-and-develop-docker-swarm/ since it was delegated very little was done to move forward swarm _> https://github.com/moby/swarmkit/commits/master , docker swarm itself (docker the company) is deprecated https://github.com/docker-archive/classicswarm . I think because there's no way to monetize swarm there's no real push for new features hence my assumption of deprecation.

This doesn't look that abandoned? https://github.com/moby/swarmkit

Or are you talking about swarm the product (versus docker swarm mode)

I don’t feel a momentum in Docker Swarm development, seeing pull requests like #3072 sitting idle for half a year, originally from 2016.

privileged not being supported is problematic, but there are PRs for it on swarmkit, see https://github.com/moby/swarmkit/pull/3072 - let's see if that gets in.

Yeah, but it seems dozens of users is not enough to really keep Docker Swarm up-to-date. privileged not working in Swarm (issue #1030 from 2016, again pull request #3072 from 2022), configs and secrets not update-able (workaround) and not write-able within container, I find that really annoying.

It is already in a different repo: moby/swarmkit

The sad thing is there are issues and even pull requests open since 2016, but it seems no one cares anymore. Mirantis bought the Docker Swarm part, but it does not show up as product on their homepage, there seems little development, despite their positive posts. Sometimes Docker employees accept some changes to the repo.

Mostly it just needs resource defaults merged and some abstract type support so load balancer config doesn't have to be entirely by labels and I would never shift from it.

This is your first mistake, imho. Last activity in their github repo is two months ago development has either been paused or halted. Use EKS.

curl -fsSL https://get.docker.com -o get-docker.sh sudo sh get-docker.sh # Install docker compose sudo curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose # Apply executable permissions to the binary sudo chmod +x /usr/local/bin/docker-compose # Run Project docker-compose up -d

Docker,

This foundation now opens the door to even more powerful concepts. You can explore more advanced concepts such as container networking, streamlining the management of complex applications with Docker Compose, and how to make your application data persistent using volumes.

sudo curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose

[ec2-user]$ sudo yum update -y [ec2-user]$ sudo yum install -y docker [ec2-user]$ sudo service docker start [ec2-user]$ sudo curl -L https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m) -o /usr/local/bin/docker-compose [ec2-user]$ sudo chmod +x /usr/local/bin/docker-compose [ec2-user]$ docker --version Docker version 20.10.23, build 7155243 [ec2-user]$ docker-compose --version Docker Compose version v2.18.1

Docker Compose Documentation

groupadd -g 997 docker gpasswd -a jenkins docker curl -L https://github.com/docker/compose/releases/tag/1.29.2/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose chmod +x /usr/local/bin/docker-compose #confirm the docker-compose is installed docker-compose version

Now that we have our basic script to run the Node application, we'll create our base image. This time we will not be using the Dockerfile as we did earlier with the Python environment, but we will pull directly from the Docker Hub registry. Because we have multi-container services, it's best to orchestrate our services from a single file rather than building the services individually from a Dockerfile, which could be a daunting task if we need to build many services. Therefore, spinning up our Node containers with Docker Compose can be pretty handy in these situations. Note that Docker compose does not replace Dockerfile. Rather, the latter is part of a process to build Docker images, which are part of containers. Docker Compose allows us to operate the Node app alongside other services (assuming we have many services we need to spin up). In our case, it will be alongside our py service.

My previous blog posts have focused on the array of options Skyramp provides for testing distributed applications deployed to Kubernetes clusters. However, Kubernetes is not required to reap the benefits of using Skyramp for test automation. You can also setup and deploy your system-under-test using Docker Compose. In this article, we'll explore how you can leverage Skyramp in conjunction with Docker Compose to streamline your microservices testing process.

From the official documentation,