You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today I started to face the following issue, while using cog push --separate-weights
Although I was able to push the model without the flag --separate-weights
On the error below, I just replaced the project and model name by and <model-name, respectively.
$ cog push --separate-weights
⚠ Cog doesn't know if CUDA 11.2.2 is compatible with PyTorch 1.13.1. This might cause CUDA problems.Building Docker image from environment in cog.yaml as r8.im/<project-name>/<model-name> ...Weights unchanged, skip rebuilding and use cached image...[+] Building 4.0s (7/7) FINISHED docker:default => [internal] load .dockerignore 0.0s => => transferring context: 22.25kB 0.0s => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 4.41kB 0.0s => resolve image config for docker.io/docker/dockerfile:1.4 1.6s => CACHED docker-image://docker.io/docker/dockerfile:1.4@sha256:9ba7531bd80fb0a858632727cf7a1 0.0s => [internal] load metadata for docker.io/nvidia/cuda:11.2.2-cudnn8-devel-ubuntu20.04 1.2s => ERROR [internal] load metadata for r8.im/<project-name>/<model-name> 2.2s => [auth] <project-name>/<model-name> -weights:pull token for r8.im 0.0s------ > [internal] load metadata for r8.im/<project-name>/<model-name>-weights:latest:------Dockerfile:2-------------------- 1 | #syntax=docker/dockerfile:1.4 2 | >>> FROM r8.im/<project-name>/<model-name>-weights AS weights 3 | FROM nvidia/cuda:11.2.2-cudnn8-devel-ubuntu20.04 4 | ENV DEBIAN_FRONTEND=noninteractive--------------------ERROR: failed to solve: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://r8.im/_token?scope=repository%3A<project-name>%2F<model-name>-weights%3Apull&service=us-docker.pkg.dev: 404 Not Foundⅹ Failed to build runner Docker image: Failed to build Docker image: exit status 1
I'm still shocked that this is still an issue after so many months. I remember wasting so many hours trying to fix this. Does anyone working at Replicate care?
Based on their Discord, my sense is they're absolutely swamped by end-users who mostly want to use the web frontends for various tools. Ideally Replicate knows this is not their core business, but I'm not so sure. I suspect they're feeling stronger PMF on the front-end than on the infra side of things.
Activity
andreemic commentedon Oct 16, 2023
same here!
usamaehsan commentedon Nov 11, 2023
facing same issue
a-sane commentedon Dec 11, 2023
facing same issue today, but week ago it works well with
--separate-weightsynie commentedon Dec 14, 2023
can we get some help on this?
ynie commentedon Dec 14, 2023
@hongchaodeng I saw you implemented this feature. Do you know what's going on? Thank you so much!!
masahiro-koga-jai commentedon Jan 31, 2024
I got a similar error, but deleting "path/to/your/cog_project/.dockerignore" and "path/to/your/cog_project/.dockerignore/.cog" files solved it for me.
hervenivon commentedon May 13, 2024
I faced a similar issue too. The docker build was failing to find the copied data.
while the file was actually here.
ynie commentedon May 13, 2024
I stopped using replicate due to the poor tech support and framework.
hervenivon commentedon May 13, 2024
What are you using as a replacement?
ynie commentedon May 13, 2024
Runpod is way better with better support.
hervenivon commentedon May 13, 2024
PS: like @masahiro-koga-jai, deleting the
.dockerignoresolved it for me. The.dockerignoreis updated duringcog build, and it obviously conflicts.emcmanus commentedon May 14, 2024
@ynie @hervenivon This and some other issues lead to a frustrating DX on Replicate, but YMMV building on Runpod. Personally my experience matches the reports here https://www.reddit.com/r/LocalLLaMA/comments/17il9n3/experience_on_runpod/
(I would definitely prefer Runpod's 4090's over A40's for image gen – they're half the price and twice as fast.)
emcmanus commentedon May 14, 2024
You may also need to
rm -r .cog/. I believe I got this error after a badcog push --separate-weights.My guess is
r8.im/<project-name>/<model-name>-weightsgets created on the first invocation, only.Deleting Cog's build folder seems to have forced it to create the missing image.
ynie commentedon May 14, 2024
I'm still shocked that this is still an issue after so many months. I remember wasting so many hours trying to fix this. Does anyone working at Replicate care?
emcmanus commentedon May 14, 2024
Based on their Discord, my sense is they're absolutely swamped by end-users who mostly want to use the web frontends for various tools. Ideally Replicate knows this is not their core business, but I'm not so sure. I suspect they're feeling stronger PMF on the front-end than on the infra side of things.
hervenivon commentedon May 14, 2024
Actually, I find
cogsuper convenient for some of the projects I'm working on, but I do agree that the UX has some flaws.Glad to find support in the community. Thanks! 🙏
narendraadloid commentedon Jun 4, 2024
yes, I had added
.cog/in.dockerignorefile, removing it solved the problem for me