Hi Start9 Community,
I’ve spent 50+ hours trying to package a working Electrs-SSL service for StartOS and discovered a critical bug in SDK 0.3.5.1 that blocks all package development.
The Problem
When running start-sdk pack
with any valid manifest, the SDK throws:
Deserialization Error: missing field `ui`
This field doesn’t exist in the official Start9 manifest specification.
The Solution
Add ui: false
as a top-level field in your manifest.yaml:
yaml
id: your-package-id
version: 0.1.0
title: Your Package Title
ui: false # <-- This fixes the SDK error
release-notes: Your release notes
license: MIT
# ... rest of manifest
What I Tried
- SDK 0.3.5.1 - Requires the undocumented
ui: false
field - SDK 0.3.4.2 - Won’t build due to missing dependencies (emver package)
- Manual packaging - Creates correct tar structure but wrong binary format
- Pre-built SDK binaries - Don’t exist (404 errors)
My Working Service
I’ve successfully built a production-ready Electrs server with SSL/TLS support via stunnel. The Docker image works perfectly, providing secure Electrum connections on port 50002. The only barrier is the SDK packaging bug.
Questions for the Community
- Has anyone successfully built packages with SDK 0.3.5.1?
- Is there a working SDK binary available somewhere?
- Can Start9 team build packages on their infrastructure for community developers?
Full Technical Details
Working Dockerfile:
dockerfile
FROM getumbrel/electrs:v0.9.10 AS electrs-base
FROM debian:bullseye
COPY --from=electrs-base /bin/electrs /usr/local/bin/electrs
RUN apt-get update && \
apt-get install -y stunnel4 openssl && \
apt-get clean && \
rm -rf /var/lib/apt/lists/*
RUN mkdir -p /etc/stunnel /var/run/stunnel /data
COPY docker_entrypoint.sh /usr/local/bin/
RUN chmod +x /usr/local/bin/docker_entrypoint.sh
EXPOSE 50001 50002
ENTRYPOINT ["/usr/local/bin/docker_entrypoint.sh"]
The service is ready for the community but blocked by this SDK issue. Any help or insights would be greatly appreciated!
Tags: #sdk Development #packaging #bug #electrs