a2nr
/
velxio
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
velxio/backend/board-indexes
History
David Montero a2df942d74 fix(docker): vendor drazzy.com board index + seed missing indexes at boot 
drazzy.com (ATTinyCore index host) has had an expired TLS certificate
since 2026-06-22 and now 301-redirects http to https, defeating the
plain-http URL pinned to sidestep its TLS issues. Two failure modes:

1. A /root/.arduino15 volume from an older image can reference the index
   in config while lacking the file; arduino-cli then fails instance
   init outright, breaking EVERY compile, not just ATtiny (issue #254).
2. backend/Dockerfile chained update-index with &&, so any uncached
   image build fails hard while the host is broken (exit 1 verified).

A stale index is harmless (ATTinyCore 1.4.1's platform archive and its
micronucleus 2.0a4 both download from github.com); a missing one is
fatal. So: vendor the index under backend/board-indexes/, copy it to
/opt/arduino15-seed in Dockerfile.standalone, and teach entrypoint.sh
to seed any missing package_*.json into /root/.arduino15 at boot,
healing stale volumes. backend/Dockerfile seeds the index directly and
makes update-index best-effort; core install lines stay strict.

Verified: removing the index reproduces the reporter's exact
'Error initializing instance' brick; after seeding, instance init
exits 0 with the host still broken.
 		2026-07-17 06:41:44 +02:00
..
README.md
…
package_drazzy.com_index.json
…

README.md

Vendored board-manager indexes

Snapshot copies of third-party Arduino board-manager indexes whose hosting has a history of outages breaking builds and fresh deployments.

Why this exists

package_drazzy.com_index.json (Spence Konde's ATTinyCore index) is served from drazzy.com, which has repeatedly had TLS problems — most recently a certificate that expired on 2026-06-22 and stayed expired for weeks, while the host also began 301-redirecting http:// to https://, defeating the plain-http URL we pin to sidestep exactly this. See issue #254.

Two things go wrong when that host is down:

  1. arduino-cli core update-index exits non-zero, so any image build that runs it in a RUN ... && ... chain fails hard.
  2. Worse, at runtime: if the arduino-cli config references the index URL but the index file was never downloaded, arduino-cli fails instance initialization outright — which breaks every compile, including boards that have nothing to do with ATtiny.

A stale index is fine (we pin ATTinyCore 1.4.1, whose platform archive and micronucleus tool both download from github.com, not drazzy.com/azduino.com). A missing index is not. So we vendor the index and seed it wherever it could be missing:

  • Dockerfile.standalone copies this directory to /opt/arduino15-seed/; docker/entrypoint.sh copies any missing package_*.json into /root/.arduino15/ at boot. This also heals pre-existing named volumes created by older images (the actual trigger of issue #254).
  • backend/Dockerfile copies the index into /root/.arduino15/ before running a now-tolerant core update-index.

Refreshing the snapshot

When drazzy.com is healthy:

curl -fL https://drazzy.com/package_drazzy.com_index.json \
    -o backend/board-indexes/package_drazzy.com_index.json

There is no need to refresh on a schedule — the file only has to be recent enough to describe the pinned ATTinyCore version.