vanya
Start the cron jobs
Dear @Guillaume, could you please specify more details? I've struggled with this for some time now.
When I simply run this from my root folder, I get:
Command 'yarn' not found, but can be installed with:
sudo apt install cmdtest
OK no big deal, I install yarn with sudo apt install cmdtest
Now I run the command again and get:
00h00m00s 0/0: : ERROR: [Errno 2] No such file or directory: 'command:prod'
Could you please help me out? 🙂
Why do the docs specifically mention "from your worker container"?9 replies
RRunPod
•Created by benjamin_n on 2/27/2025 in #⛅｜pods-clusters
Spot instances dissappearing??
Isn't that just normal spot instance behavior? That is the reason they are so cheap. From the docs:
On-Demand Pods can run forever without interruptions with resources dedicated to your Pod. They do incur higher costs than Spot Pods.
Spot Pods use spare compute capacity, allowing you to bid for those compute resources. Resources are dedicated to your Pod, but someone else can bid higher or start an On-Demand Pod that will stop your Pod. When this happens, your Pod is given a signal to stop 5 seconds prior with SIGTERM, and eventually, the kill signal SIGKILL after 5 seconds. You can use volumes to save any data to the disk in that 5s period or push data to the cloud periodically.
5 replies
RRunPod
•Created by tampe125 on 2/25/2025 in #⛅｜pods-clusters
Authenticate to AWS ECR private repository
error pulling image: Error response from daemon: pull access denied for x, repository does not exist or may require 'docker login':
denied: requested access to the resource is denied
error creating container: unauthorized to use image x
7 replies
RRunPod
•Created by tampe125 on 2/25/2025 in #⛅｜pods-clusters
Authenticate to AWS ECR private repository
I got the same issue but with normal Docker ... I feel like most people use runpod to spin up some template :p
7 replies