Known Issues and FAQ

Lightly Worker is slow when working with long videos

We are working on this issue internally. For now we suggest to split the large videos into chunks. You can do this using ffmpeg and without losing quality. The following code just breaks up the video in a way that no re-encoding is needed.

ffmpeg -i input.mp4 -c copy -map 0 -segment_time 01:00:00 -f segment -reset_timestamps 1 output%03d.mp4

What exactly happens here?

input.mp4, this is your input video
-c copy -map 0, this makes sure we just copy and don’t re-encode the video
-segment_time 01:00:00 -f segment, defines that we want chunks of 1h each
-reset_timestamps 1, makes sure we reset the timestamps (each video starts from 0)
output%03d.mp4, name of the output vidoes (output001.mp4, output002.mp4, …)

Lightly Worker Crashes when running with GPUs

You run the docker with –gpus all and encounter the following error?

Error response from daemon: could not select device driver "" with capabilities: [[gpu]].

This error might be caused because your docker installation does not support GPUs.

Try to install nvidia-docker following the guide here.

Shared Memory Error when running Lightly Worker

The following error message appears when the docker runtime has not enough shared memory. By default Docker uses 64 MBytes. However, when using multiple workers for data fetching lightly.loader.num_workers there might be not enough.

ERROR: Unexpected bus error encountered in worker. This might be caused by insufficient shared memory (shm).
Traceback (most recent call last):
File "/opt/conda/envs/env/lib/python3.7/multiprocessing/queues.py", line 236, in _feed
    obj = _ForkingPickler.dumps(obj)
File "/opt/conda/envs/env/lib/python3.7/multiprocessing/reduction.py", line 51, in dumps
    cls(buf, protocol).dump(obj)
File "/opt/conda/envs/env/lib/python3.7/site-packages/torch/multiprocessing/reductions.py", line 321, in reduce_storage
    fd, size = storage._share_fd_()
RuntimeError: unable to write to file </torch_31_1030151126>

To solve this problem we need to increase the shared memory for the docker runtime.

You can change the shared memory to 512 MBytes by adding –shm-size=”512m” to the docker run command:

# example of docker run with setting shared memory to 512 MBytes
docker run --shm-size="512m" --gpus all

Lightly Worker crashes because of too many open files

The following error message appears when the docker runtime has not enough file handlers. By default Docker uses 1024. However, when using multiple workers for data fetching lightly.loader.num_workers this might be not enough. As file handlers are used at many different parts of the code, the actual error message may differ. Internet connections like for connecting to the Lightly API also use file handlers.

<Error [Errno 24] Too many open files>

To solve this problem we need to increase the number of file handlers for the docker runtime.

You can change the number of file handlers to 90000 by adding –ulimit nofile=90000:90000 to the docker run command:

# example of docker run with 90000 file handlers
docker run --ulimit nofile=90000:90000 --gpus all

More documentation on docker file handlers is providided here.

Permission denied for input created with sudo

There are some problems if the input directory was created with root/ sudo and the container tries to access it. This can be solved by making the files readable:

# make subdirectories browsable
find MY_INPUT_DIR -type d -exec chmod 755 {} +

# make the files themselves readable
find MY_INPUT_DIR -type f -exec chmod 644 {} +

Error when using S3 fuse and mounting to docker

If you use docker in combination with S3 fuse you might stumble across an issue that the docker container can’t create the mount path for the input directory.

docker: Error response from daemon: error while creating mount source path \
'/home/ubuntu/mydataset/': mkdir /home/ubuntu/mydataset: file exists.

You can resolve this problem by following the guide here: https://stackoverflow.com/a/61686833

uncomment user_allow_other option in the /etc/fuse.conf file
when you mount the bucket using s3fs use the -o allow_other option.
```
s3fs my-s3-bucket /s3-mount -o allow_other -o use_cache=/tmp
```

Token printed to shared stdout or logs

The token (along with other Hydra configuration) will be printed to stdout, and so could appear in logs in an automated setup.

docker run --rm -it \
    -v {OUTPUT_DIR}:/home/shared_dir \
    lightly/worker:latest \
    token=MYAWESOMETOKEN \
    ...

This can be avoided by setting your token via the LIGHTLY_TOKEN environment variable:

docker run --rm -it \
    -e LIGHTLY_TOKEN=MYAWESOMETOKEN
    -v {OUTPUT_DIR}:/home/shared_dir \
    lightly/worker:latest \
    ...

No permission to pull the docker image

Please make sure the authentication succeeded as described in the Download the Docker Image guide.

If you still can’t pull the docker image it might be that the docker config is causing the problem.

You can check the config using the following command:

cat ~/.docker/config.json

You should see a section with the key for authentication. If you also see a section about the credHelpers they might overrule the authentication.

The credHelpers can overrule the key for certain URLs. This can lead to permission errors pulling the docker image.

The Lightly docker images are hosted in the European location. Therefore, it’s important that pulling from the eu.gcr.io domain is using the provided credentials.

There are two ways to solve the problem:

You can delete the config and run the authentication again.

rm ~/.docker/config.json

cat container-credentials.json | docker login -u _json_key --password-stdin https://eu.gcr.io

You can work with two configs. We recommend creating a dedicated folder for the Lightly docker config.

mkdir -p ~/.docker_lightly/

cat container-credentials.json | docker --config ~/.docker_lightly/ login -u _json_key --password-stdin https://eu.gcr.io

docker --config ~/.docker_lightly/ pull  eu.gcr.io/boris-250909/lightly/worker:latest

Whenever you’re pulling a new image (e.g. updating Lightly) you would need to pass it the corresponding config using the –config parameter.