Nomad VS Docker Compose

I believe Nomad is hailed as the replacement: https://github.com/hashicorp/nomad#readme

I would caution one against "javascript framework syndrome:" bah, this framework is too complicated, I just want something simpler ... ok, it doesn't work right in all circumstances, I'll just add this one feature(, ... ok, maybe just this one other feature)+ ... bah, this framework is too complicated!

In a previous hackathon, data analyst Chris Migirdic built an IDE where you present your own time series data/problem, and a layer could be provided over it to make time-series predictions. This iteration was quickly dubbed “BYOSQL,” or Bring Your Own SQL, by participants as he explained one could write any SQL query against Lob’s data warehouse, and you'd be able to fit a time series model over that. The most obvious application for Lob is evaluating mailpiece data. Another improvement over the previous version was performance; much of this was attributed to a shift to deployment in Nomad. Finally, another benefit of the program is to pick up what kinds of queries people are running and get an idea of what prediction problems our developers are trying to solve.

That being said, it hasn't kept similar offerings from continuing to pop up as a "less complex" solution. Take Nomad for instance.

HashiCorp Nomad | Full time | Remote

https://www.nomadproject.io

Want to work on an alternative to Kubernetes made by the creators of Terraform, Consul, Vagrant, and Vault? Come work on Nomad at HashiCorp! Our team builds and maintains a highly-scalable, flexible distributed cluster orchestrator. Nomad helps teams run varied workloads including containers, VMs, and raw binaries. Cloudflare, PagerDuty, Roblox, Pandora, and many other large organizations run Nomad in production today.

We are currently looking for both backend and frontend engineers interested in solving hard problems in the DevOps space, tackling interesting distributed systems challenges, and/or working on open source software.

Our stack: Golang & Ember (experience in either is nice to have, but not a hard requirement)

Here’s a link to a full job posting: https://www.hashicorp.com/job/3990643

Also, feel free to reach out to me, a PM on the team, at mnomitch (at) hashicorp (dot) com

In this post, I want to show how you can implement your own tool using the HCL format. The HCL configuration format is used by all the amazing HasiCorp tools like Terraform, Vault, and Nomad.

Nomad Client (www.nomadproject.io - Container Orchestration)

Shoulda been more clear, sorry; I don't use docker or docker swarm. I'm using nomad as my orchestration system (and the cluster I have running at home is exclusively podman nodes, so no docker even). I need to rewrite the docker-compose in nomad's HCL format, which usually this only takes a few minutes but appwrite's docker-compose is pretty dense. I might write a script to do it, tbh.

I think it's often better to "pick your poison" in terms of cloud providers and commit to it, with a rough migration plan that you can execute if you have to. There'll be common patterns in your systems that can be repeated if a large-scale lift-and-shift has to happen for some reason. But it's never easy, and I've found different clouds to have their own idiosyncrasies that make migration difficult - larger migrations will inevitably take time, effort, and lots of planning.

If you're looking for alternatives, or something lighter weight than Kubernetes, I've used Nomad (plus Terraform and Ansible) and some shell scripts to get repeatable clusters deployed and migrated between cloud providers: https://www.nomadproject.io/

Nomad can also work. It's relatively popular and advertised as less complicated than K8's https://www.nomadproject.io/

you should introduce her to https://docs.docker.com/compose/ and marry her. order does not matter.

VERSION=$(curl --silent https://api.github.com/repos/docker/compose/releases/latest | jq .name -r) curl -L "https://github.com/docker/compose/releases/download/${VERSION}/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose; chmod +x /usr/local/bin/docker-compose;

Documentation

You can choose the official docker-compose that will search for the Docker API (Podman can expose both native and Docker-legacy API). Unfortunately, as all the procedure that goes through the API, rootless can not be used.

my problem similar to https://github.com/docker/compose/issues/9264

Compose is a tool for defining and running multi-container Docker applications. With Compose, you use a YAML file to configure your application’s services. Then, with a single command, you create and start all the services from your configuration.

Docker swarm was introduced to plug this deficiency and allow docker-compose to treat a pool of VMs as one large computer. In practice we found early versions of Docker Swarm didn't work particularily well, especially when the number of nodes went above 10 and stuff like load balancers and scaling became hard to do in a single compose file.... in short this stuff is hard to do at scale. To give credit, docker swarm introduced a new concept of "stacks", but this introduced incompatible changes to the docker compose syntax, which in my companies case marooned us on docker compose v2.....

Docker-Compose

Traefik is a reverse http proxy, it works specially well with docker and docker-compose environments. Traefik will receive all your incoming web requests and redirect them to Docker containers.

#!/bin/bash # treat unset variables as an error and exit immediately. set -u # exit immediately if any command returns a non-zero exit code set -e VERSION="1.26.0" sudo curl -L "https://github.com/docker/compose/releases/download/$VERSION/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose sudo chmod +x /usr/local/bin/docker-compose sudo ln -s /usr/local/bin/docker-compose /usr/bin/docker-compose