#Long running task--visibility and or cpu and memory allocation?

1 messages · Page 1 of 1 (latest)

fleet sentinel
#

I've finally convinced dagger to build some of my docker containers (using pants and ssh mounts, etc)...

...and it built several, but on one it's gone off into space for about an hour and still says "Long running tasks..." listing that docker image build. That shouldn't take more than about 10 minutes particularly on this machine.

So something's clearly off, but I can't tell if it's slow, hung up on something, or what the problem is; restarting it with --log-level=debug didn't show up much either. htop doesn't reveal a ton of activity.

It's odd to me because it built the other containers fine. Could this be a resources problem somehow? Is there a default constraint for memory/cpu usage that may cause it to thrash that I could bump up?

Sorry so vague; not sure how to proceed yet.

cold kayak
#

Hi @fleet sentinel , are you using the CUE or Go SDK?