ci: add workflow to build and push Docker image
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 7
- Avg merge
- 4h 1m
- Merged PRs (30d)
- 6
Description
Problem
There is no CI workflow that builds or pushes the livepeer/subgraph Docker image. The image doesn't exist on Docker Hub, and the Docker-based test infrastructure (docker-compose.test.yml) has been broken without anyone noticing since CI never exercises it.
Currently all Docker builds are manual, and the test script (yarn test) relies on a Docker image that is never built or published by CI.
Plan
- First: Fix the
docker-composev1 issues (#220) and create a PR- Replace
docker-composewithdocker composeinpackage.jsonscripts - Remove
--cache-fromfor non-existent image indocker:build - Remove deprecated
version: "3"from compose files - Update stale container images (
ipfs/go-ipfs, etc.)
- Replace
- Then: Add a GitHub Actions workflow that:
- Builds the
livepeer/subgraphDocker image on PRs (smoke test) - Pushes the image to a container registry (Docker Hub or GHCR) on merges to
mainand version tags - Optionally runs the
docker-compose.test.ymlintegration test suite as part of CI
- Builds the
This would catch issues like the recent node:14 / node:20 Dockerfile breakage (#219) before they land.
Related
- #220 —
docker-composev1 dependency breaks test and start scripts
🤖 Generated with Claude Code
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the package.json scripts, docker-compose.test.yml, and Dockerfile, and review issue #220 before designing the workflow. Verify that the Docker image builds on pull requests, that merges to main and version tags publish it to the selected registry, and that the Docker-based tests are exercised in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, github-actions, typescript
- Domain
- build-system, ci-cd, devops, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100