Bug #4977: [Crunch] "stdbuf": executable not found in $PATH - Arvados

Actions

Copy link

Bug #4977

closed

[Crunch] "stdbuf": executable not found in $PATH

Added by Tim Pierce almost 10 years ago. Updated over 7 years ago.

Status:

Resolved

Priority:

Normal

Assigned To:

Category:

Crunch

Target version:

Deferred

Story points:

Description

Job qr1hi-8i9sb-awaor08g6odb1c2 failed with the following error message:

2015-01-14_16:31:21 qr1hi-8i9sb-awaor08g6odb1c2 2497 0 stderr exec: "stdbuf": executable file not found in $PATH2015/01/14 16:31:21 Error response from daemon: Cannot start container 451b8d41f1c32137a6ceec27adaafe9b7fbfa710690920e9b053e5eb2617191b: exec: "stdbuf": executable file not found in $PATH

Additional jobs which failed for the same reason:

Each of these jobs attempted to run one of the following docker images (both variants of the bcosc/lobstrflat image):

d36137539aeb14178a1e83df0882d04a+545
a4c18a346e385a756fd993f35d45dc85+629

Rebuilding the lobstrflat image from scratch resolved the problem.

Actions

Copy link

Updated by Tom Clegg almost 10 years ago

Target version changed from Bug Triage to Deferred

Actions

Copy link

Updated by Brett Smith almost 10 years ago

Target version changed from Deferred to Bug Triage

Given that the bug has happened consistently with this one Docker image, and only with this one Docker image, I strongly suspect that there's some issue with the Docker image itself. It would be good to track down the issue and document it, but I've spent a couple of hours on that with no luck reproducing the issue. So we're going to hold off to wait and see this happen again—if it does, we'll probably have an easier time tracking down the issue by comparing two affected Docker images. We're happy to un-defer this when that happens.

Actions

Copy link