All three first-boot defects are cured: the Python environment has the module `superset db upgrade` was missing (it died with `ModuleNotFoundError: No module named 'rich'`), first boot stops superset.service before migrating so a boot-time gunicorn cannot race the SQLite metastore, and the generated dcaadmin sign-in is verified against the running service before the credential file is written. http://<VM-IP>:8088/ answers and /var/lib/superset/admin-password is present.
If you deployed this VM before 2026-09-16, 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:
Image change: see the pull request.
Source: the Marketplace live version set for this offer, read from Partner Center on 2026-09-16. New deployments take the newest version by default.
| Application ports | 8088 (Superset web UI) |
|---|---|
| Open in browser | http://<VM-IP>:8088/ |
| Admin credential file | sudo cat /var/lib/superset/admin-password |
| Sign in as | dcaadmin |
| Service(s) | superset |
| Configuration | /etc/default/superset (SUPERSET_SECRET_KEY, generated at first boot); /opt/superset/ |
| Logs | journalctl -u superset -f |
| Version | Apache Superset 6.1.0 (Python 3.12 venv, gunicorn) |
| Platform | Ubuntu 24.04 LTS |
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 /var/lib/superset/admin-passwordSign in as dcaadmin.
Sign in as dcaadmin (not `admin`) with the password in the file.
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.