## TL;DR

The --max-active-adapters argument for Lorax does exist; if a fresh pull doesn't show it, update your Docker image (there was a Docker build cache issue hiding it). One caveat from the maintainer: it caps the number of concurrent adapters, not their total size, so very large adapters can still blow GPU memory. The longer-term idea is a --max-active-adapter-memory flag that reserves GPU memory instead of counting adapters.

## When to use

You are seeing this: One caveat from the maintainer: it caps the number of concurrent adapters, not their total size, so very large adapters can still blow GPU memory. Use this skill when you run into "add --max-active-adapters argument".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Steps

1. The --max-active-adapters argument for Lorax does exist; if a fresh pull doesn't show it, update your Docker image (there was a Docker build cache issue hiding it). One caveat from the maintainer: it caps the number of concurrent adapters, not their total size, so very large adapters can still blow GPU memory. The longer-term idea is a --max-active-adapter-memory flag that reserves GPU memory instead of counting adapters.

## Edge cases

- One caveat from the maintainer: it caps the number of concurrent adapters, not their total size, so very large adapters can still blow GPU memory.