{"pageProps":{"postData":{"id":"2021-10-05-running-nomad-on-raspberry","contentHtml":"<p>Hi everyone, in this post I explain the Hashicorp Nomad installation process to manage Docker containers on my Raspberry Pi.</p>\n<p>Definition of Nomad \"A simple and flexible workload orchestrator to deploy and manage containers and non-containerized applications across on-prem and clouds at scale.\" according to the <a href=\"%22https://www.nomadproject.io/%22\">website</a>.</p>\n<p>I have been using the Raspberry Pi OS 64 bits on a Raspberry Pi 4, this OS is based on Debian 10 for arch arm64 at the time of writing this article.</p>\n<p>The first step is to get the single binary and copy it to folder /usr/local/bin</p>\n<p>The binary can be downloaded from <a href=\"%22https://www.nomadproject.io/downloads%22\">Nomad website</a>.</p>\n<p>Unzip the binary, change the permission and move it to /usr/local/bin</p>\n<pre><code class=\"language-sh\">sudo chown root:root nomad\n\nsudo mv nomad /usr/local/bin\n</code></pre>\n<p>After that, you need to create a SystemD script to enable and start a service.</p>\n<pre><code class=\"language-sh\">sudo touch /etc/systemd/system/nomad.service\n</code></pre>\n<p>And add the following content.</p>\n<pre><code class=\"language-config\">[Unit]\nDescription=Nomad\nDocumentation=https://www.nomadproject.io/docs/\nWants=network-online.target\nAfter=network-online.target\n\n# When using Nomad with Consul it is not necessary to start Consul first. These\n# lines start Consul before Nomad as an optimization to avoid Nomad logging\n# that Consul is unavailable at startup.\n#Wants=consul.service\n#After=consul.service\n\n[Service]\nExecReload=/bin/kill -HUP $MAINPID\nExecStart=/usr/local/bin/nomad agent -config /etc/nomad.d\nKillMode=process\nKillSignal=SIGINT\nLimitNOFILE=65536\nLimitNPROC=infinity\nRestart=on-failure\nRestartSec=2\n\n## Configure unit start rate limiting. Units which are started more than\n## *burst* times within an *interval* time span are not permitted to start any\n## more. Use `StartLimitIntervalSec` or `StartLimitInterval` (depending on\n## systemd version) to configure the checking interval and `StartLimitBurst`\n## to configure how many starts per interval are allowed. The values in the\n## commented lines are defaults.\n\n# StartLimitBurst = 5\n\n## StartLimitIntervalSec is used for systemd versions >= 230\n# StartLimitIntervalSec = 10s\n\n## StartLimitInterval is used for systemd versions &#x3C; 230\n# StartLimitInterval = 10s\n\nTasksMax=infinity\nOOMScoreAdjust=-1000\n\n[Install]\nWantedBy=multi-user.target\n\n</code></pre>\n<p>Add a nomad config file to /etc/nomad.d/nomad.hcl</p>\n<pre><code class=\"language-hcl\">data_dir = \"/opt/nomad/data\"\nbind_addr = \"0.0.0.0\"\n\nserver {\n  enabled = true\n  bootstrap_expect = 1\n}\n\nclient {\n  enabled = true\n  servers = [\"127.0.0.1:4646\"]\n}\n</code></pre>\n<p>Enable and start a service, check the service status.</p>\n<pre><code class=\"language-sh\">sudo systemctl enable nomad\n\nsudo systemctl start nomad\n\nsudo systemctl status nomad\n</code></pre>\n<p>Finally, access the <a href=\"%22http://localhost:4646%22\">http://localhost:4646</a> and the see ui manager of Nomad Hashicorp.</p>\n<p>References</p>\n<ul>\n<li><a href=\"https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul\">https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul</a></li>\n</ul>\n","title":"Running Hashicorp Nomad on Raspberry","date":"2021-10-05"}},"__N_SSG":true}