replicate / replicate/cog

Broken docker leads to `cog push` hang?

Open
#941 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

go type/bug
Dominant language
Go
Stars
9.5k
Forks
696
Avg merge
7d 19h
Merged PRs (30d)
2

Description

A user reported in Discord that their cog push command was hanging after printing just

Building Docker image from environment in cog.yaml as r8.im/.../...

It turned out to be a crashed or hung Docker daemon. Perhaps we can set a timeout or something on our use of the Docker daemon and report the problem to the user?

https://discord.com/channels/775512803439280149/1074047343529300131

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Trace the cog push Docker build path and reproduce the hang with a crashed or unavailable Docker daemon. Define a timeout and a clear user-facing error, then verify that cog push no longer waits indefinitely.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
cli, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.