Derek Coleman & Associates Inc logoDerek Coleman & Associates Inc

Home / Support / etcd on Ubuntu 24.04 LTS

etcd on Ubuntu 24.04 LTS — Support & Quick Start

etcd on Ubuntu 24.04 LTS — etcd is the strongly consistent, distributed key-value store behind Kubernetes — used for configuration, service discovery and leader election. Published by Derek Coleman & Associates Inc on the Azure Marketplace, deployed in your own Azure subscription.

Email support Product page Azure Marketplace listing

Fixed on image version 2026.1012.1424 (published 2026-10-12)

The image ships etcd.service disabled and first boot starts etcd exactly once, so the new member's first start can no longer be interrupted. First boot then creates the root user with a password generated on your VM, enables authentication, proves the credential and writes /root/etcd-admin-credentials.txt and the login message.

If you deployed this VM before 2026-10-12, it came from the older image and is not changed by the new publication — redeploy from the current Marketplace version, or apply the one-time repair below:

  1. VMs deployed from image 2026.930.2005 whose first boot completed (/root/etcd-admin-credentials.txt exists) are fine. If the file does not exist, that VM's first boot hit the restart race and cannot recover by rebooting: it holds no data yet, so delete it and deploy again.

Image change: see the pull request.

Source: the Marketplace live version set for this offer, read from Partner Center on 2026-10-12. New deployments take the newest version by default.

At a glance

Application ports2379 (client) and 2380 (peer) — both bound to 127.0.0.1 only; no inbound application port is open
Admin credential filesudo cat /root/etcd-admin-credentials.txt
Sign in asroot (etcd auth is enabled; the file also walks through exposing the node safely)
Service(s)etcd
Configuration/etc/systemd/system/etcd.service (listen/advertise URLs); data in /var/lib/etcd/
Logsjournalctl -u etcd -f
Versionetcd 3.6.15 (single node, authentication enabled)
PlatformUbuntu 24.04 LTS

Quick start

  1. Deploy from the Azure Marketplace (Get It Now → Create), choosing your SSH key at the Administration step.
  2. Allow inbound SSH (22) for yourself only — etcd listens on localhost until you deliberately add TLS and rebind it.
  3. SSH in and use etcdctl with the generated root credentials (see First login below).
  4. For clients on other hosts, add TLS, rebind the listen URLs, open 2379 in ufw to their CIDR and in the NSG.

First login / credentials

This image generates its admin credential on the VM at first boot — nothing is pre-set. SSH into the VM with the username + key you chose at deploy, then print the generated credential:

ssh <your-username>@<VM-IP>
sudo cat /root/etcd-admin-credentials.txt

Sign in as root (etcd auth is enabled; the file also walks through exposing the node safely).

  1. Print the credential file: the etcd root password generated at first boot (authentication is already enabled).
  2. Verify locally: etcdctl --endpoints=http://127.0.0.1:2379 --user 'root:<password>' endpoint health; create scoped users/roles with `etcdctl --user root:<pw> user add …`.
  3. etcd is unreachable from other hosts by design. To expose or cluster it: provision client and peer TLS first, rebind --listen-client-urls/--listen-peer-urls in the unit, `sudo ufw allow from <cidr> to any port 2379`, and scope the NSG.

Auth is enabled; the root password is in the file. The plain-HTTP listeners are loopback-only — never expose 2379/2380 without TLS.

Still stuck?

Email support@dcassociatesgroup.com (response within 1 business day) or send a message via the contact form. Include the offer name, VM size, region, and any log output — sudo journalctl -u <service> -n 100 usually tells the story.