dearsky/wifi-densepose
1
0
Fork 0
Code Issues 20 Pull Requests 5 Actions Packages Projects Releases 1 Wiki Activity

Fix Docker image path to use GitHub Container Registry #48

Closed
04cb wants to merge 1 commits from fix/docker-image-path-ghcr into main
pull from: fix/docker-image-path-ghcr
merge into: dearsky:main
Conversation 2 Commits 1 Files Changed 1 +3 -3
04cb commented 2026-03-01 12:55:45 +08:00 (Migrated from github.com)
Copy Link

Fixes #43

The README documented Docker images at docker.io/ruvnet/wifi-densepose:latest but the CI pipeline publishes to GitHub Container Registry at ghcr.io/ruvnet/wifi-densepose:latest. This caused docker pull failures for users.

This fix updates the README to use the correct ghcr.io path for pre-built images and updates the Docker badge to point to the GitHub container package page.

Fixes #43 The README documented Docker images at docker.io/ruvnet/wifi-densepose:latest but the CI pipeline publishes to GitHub Container Registry at ghcr.io/ruvnet/wifi-densepose:latest. This caused docker pull failures for users. This fix updates the README to use the correct ghcr.io path for pre-built images and updates the Docker badge to point to the GitHub container package page.
ruvnet commented 2026-03-01 14:00:34 +08:00 (Migrated from github.com)
Copy Link

Thanks for flagging this @04cb — however the Docker Hub image is actually live and pullable:

$ docker pull ruvnet/wifi-densepose:latest
Digest: sha256:7b42feffa6a27588de9be0a7d4f98064af28ff87cd36071852c4d4bf1e4c192c
Status: Image is up to date for ruvnet/wifi-densepose:latest

The image was published to Docker Hub at docker.io/ruvnet/wifi-densepose, not GHCR. I just verified the pull succeeds and the container runs correctly with all API endpoints responding.

We also recently fixed a port mismatch bug (44b9c30d) where the Dockerfile wasn't passing --http-port 3000 --ws-port 3001 — that'll be in the next published image.

Closing as the Docker Hub path is correct and functional. If you're still hitting pull failures, it may have been a temporary Docker Hub issue or authentication requirement — please reopen if so.

Thanks for flagging this @04cb — however the Docker Hub image is actually live and pullable: ```bash $ docker pull ruvnet/wifi-densepose:latest Digest: sha256:7b42feffa6a27588de9be0a7d4f98064af28ff87cd36071852c4d4bf1e4c192c Status: Image is up to date for ruvnet/wifi-densepose:latest ``` The image was published to **Docker Hub** at `docker.io/ruvnet/wifi-densepose`, not GHCR. I just verified the pull succeeds and the container runs correctly with all API endpoints responding. We also recently fixed a port mismatch bug (44b9c30d) where the Dockerfile wasn't passing `--http-port 3000 --ws-port 3001` — that'll be in the next published image. Closing as the Docker Hub path is correct and functional. If you're still hitting pull failures, it may have been a temporary Docker Hub issue or authentication requirement — please reopen if so.
ruvnet commented 2026-03-01 14:00:51 +08:00 (Migrated from github.com)
Copy Link

Closing — Docker Hub image is live and pullable. See comment above.

Closing — Docker Hub image is live and pullable. See comment above.

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 security
Security-related issues and hardening
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dearsky
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dearsky/wifi-densepose#48
Delete Branch "fix/docker-image-path-ghcr"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?