Skip to content

chore(ci): add Docker Hub publish workflow for linkpool/erpc - #15

Closed
shpookas wants to merge 1 commit into
mainfrom
chore/dockerhub-publish-workflow
Closed

chore(ci): add Docker Hub publish workflow for linkpool/erpc#15
shpookas wants to merge 1 commit into
mainfrom
chore/dockerhub-publish-workflow

Conversation

@shpookas

@shpookas shpookas commented Aug 3, 2026

Copy link
Copy Markdown

Summary

  • Add workflow_dispatch workflow that builds the repo Dockerfile and pushes docker.io/linkpool/erpc:<tag>
  • Checkout is configurable (ref, default feat/websocket-support) so we can publish tip-pin / WS builds without merging that branch to main
  • Platforms default to linux/amd64 (matches current ma-production nodes)

Secrets required (before first run)

Repo secrets on linkpoolio/erpc:

  • DOCKERHUB_USERNAME — Hub user with write to org linkpool
  • DOCKERHUB_TOKEN — access token for that user

Someone with Hub/linkpool admin (or org secrets admin) needs to add these. Until then the workflow will fail at login.

How to publish PR14 image after merge + secrets

  1. Actions → Publish to Docker Hub → Run workflow
  2. tag: pin-near-tip-getblock-test9 (or a new tag)
  3. ref: feat/websocket-support
  4. Bump internal-erpc values to docker.io/linkpool/erpc:<tag>

Test plan

  • Secrets added
  • Dispatch once; job reaches Hub login + push
  • docker pull docker.io/linkpool/erpc:<tag> works; digest noted for Argo values

Made with Cursor

Manual publish of experiment/prod tags from an arbitrary git ref
(default feat/websocket-support). Requires DOCKERHUB_USERNAME and
DOCKERHUB_TOKEN repo secrets with write to the linkpool Hub org.

Co-authored-by: Cursor <cursoragent@cursor.com>
@shpookas

shpookas commented Aug 3, 2026

Copy link
Copy Markdown
Author

Closing: we do not control merges to main on this repo. Workflow file lives on feat/websocket-support for reference; publish path stays local/personal Docker Hub until Hub org write access exists.

@shpookas shpookas closed this Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant