You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Core |`langflowai/langflow:core-VERSION`|`ghcr.io/langflow-ai/langflow:core-VERSION`| The Langflow service, UI, core components, and no provider bundle distributions |
13
+
| Default |`langflowai/langflow:VERSION`|`ghcr.io/langflow-ai/langflow:VERSION`| Core plus the curated provider set used by the standard Langflow installation |
14
+
| Full |`langflowai/langflow-all:VERSION`|`ghcr.io/langflow-ai/langflow-all:VERSION`| Default plus the long-tail `lfx-bundles` provider inventory |
15
+
16
+
The full profile intentionally uses a separate `langflow-all` repository. The
17
+
core and default profiles use different tags in the `langflow` repository.
18
+
Core omits all provider distributions; default omits the long-tail
19
+
`lfx-bundles` distribution. A flow that references an omitted component cannot
20
+
run until you select a profile that provides it or build that provider into a
21
+
derived image.
22
+
23
+
## Pin a release
24
+
25
+
Use a versioned tag in deployments:
26
+
27
+
```yaml
28
+
services:
29
+
langflow:
30
+
image: langflowai/langflow:core-1.12.0
31
+
```
32
+
33
+
The moving tags are `langflowai/langflow:core-latest`,
34
+
`langflowai/langflow:latest`, and `langflowai/langflow-all:latest`,
35
+
respectively. They are convenient for local evaluation, but they can select a
36
+
new release without a configuration change. Production deployments should pin
37
+
a version tag and, when reproducibility is required, the registry digest:
0 commit comments