Minimal gitlab configuration is failing to cp to default $OUT about clusterfuzzlite HOT 13 OPEN

2023-04-26 18:30:07,341 - root - INFO - Docker container: .

This is the cause. The OUT dir being not set properly is a subsequent error. Maybe we could add some sanity check. The issue is described and a fix provided in #126.

from clusterfuzzlite.

hmm.
Echoing $OUT in the dockerfile returns /out but the docker run command is OUT=/builds/33190/build-out Is this expected? Maybe I can force create the latter somehow.

from clusterfuzzlite.

I think this is expected. /out is something inherited from OSS-Fuzz.
Is the repo you are doing this on public?
What version of gitlab's CI platform are you using?
@catenacyber do you have any ideas?

from clusterfuzzlite.

DO you know why /builds/33190 might be a file instead of a dir?

from clusterfuzzlite.

Gitlab 15.11.0-ee with 15.11 runners
Private repo unfortunately. I'm evaluating clusterfuzzlite for my company.
I'm not sure at what layer that folder gets created, but I don't think it is getting made. At least based on my attempts to put ls -l in the dockerfile to see what's going on

from clusterfuzzlite.

Also, this env var here is empty if I echo it

# Get gitlab's container id
- export CFL_CONTAINER_ID=`cut -c9- < /proc/1/cpuset`

Seems like a good clue..?

I'll pair with our dev ops person when they're available to get some more information

from clusterfuzzlite.

What kind of Gitlab runner do you have ?

This looks like cp $(which llvm-symbolizer) $OUT/ in compile is failing...

from clusterfuzzlite.

These are self-hosted runners using kubernetes and helm.

I'm not sure what the root issue is, but I think I just need to figure out how to pass $CI_JOB_ID down from .gitlab-ci.yml into the Dockerfile so I can explicitly create that directory

from clusterfuzzlite.

Looks like the docs are already updated. Is there anything I need to do to update or will the image automatically pull cfl changes?

from clusterfuzzlite.

I just updated the docs, I think you still need to recopy the example in the docs.

from clusterfuzzlite.

The suggested .gitlab-ci.yaml change wasn't the silver bullet I was hoping for. What does CFL_CONTAINER_ID do? It still isn't populated for me with this syntax.

from clusterfuzzlite.

It depends if you are using docker in docker, if you aren't, it's not used for anything. If you are:
It's supposed to give a unique id to each run so they can write to a directory that persists between containers. If you have a substitute for this, use that.

from clusterfuzzlite.

So you are trying to run ClusterFuzzLite on a Kubernetes executor? This is currently not supported, though I'd love to see this. I currently use a private runner on a VM or bare metal that runs a Docker executor which has docker.sock mounted as a volume inside the containers.

from clusterfuzzlite.