LabVIEW Docker container images — run headless LabVIEW in Docker for LabVIEW automation, automated builds, CI/CD pipelines, static code analysis, and more on Linux and Windows.
This project provides prebuilt LabVIEW container images and Dockerfiles for running LabVIEW and LabVIEWCLI in Docker. Use them for LabVIEW headless builds, LabVIEW CICD integration, MassCompile, VI Analyzer, RunVI, build specs, and other LabVIEWCLI operations — with GitHub Actions, GitLab CI/CD, Jenkins, Azure DevOps, and more.
Key features:
- Prebuilt Linux and Windows LabVIEW Docker container images on Docker Hub
- Headless LabVIEW execution (LabVIEW 2026 Q1+) — no display or GUI required
- Ready-to-use GitHub Actions and GitLab CI/CD workflow examples
- Dockerfiles for building custom LabVIEW container images with your own tools and dependencies
Table of Contents
- Overview
- Prerequisites
- Getting Started
- Examples & CI/CD Integration
- Releases & Changelog
- Frequently Asked Questions
- License
National Instruments officially supports LabVIEW containers on both Windows and Linux to streamline LabVIEW automation and LabVIEW CICD workflows. The base images are publicly available on Docker Hub:
Docker Hub: nationalinstruments/labview
- Docker Engine or Docker CLI (version 20.10+)
- At least 8 GB RAM (16 GB for Windows containers) and 4 CPU cores available (recommended)
- Internet connection for downloading and/or building your own image.
- Familiarity with Docker commands and concepts is helpful, especially if you plan to use or extend the Dockerfile.
We offer two delivery options depending on your use case:
Prebuilt LabVIEW container images on Docker Hub include a ready-to-use LabVIEW installation. Use these for a plug-and-play experience with minimal configuration.
- Image name:
nationalinstruments/labview:<release>-<platform> - See Releases for available LabVIEW Docker container tags.
- Full guide: Using Prebuilt Images — image specs, pulling, running, and examples.
Beta releases: We publish beta versions for every new LabVIEW release with tag <release>-<platform>-beta on Docker Hub.
For teams that need more control — adding custom tools, scripts, network settings, or dependencies — we provide official Dockerfiles.
- Full guide: Build Your Own Image — prerequisites, Dockerfile overview, and build instructions.
The Examples guide covers interactive usage of LabVIEW containers — pulling images, running LabVIEWCLI commands, mounting volumes, debugging headless LabVIEW, and more.
For LabVIEW automated builds and LabVIEW CICD pipeline integration:
- GitHub Actions: CI/CD Examples — MassCompile and VI Analyzer workflows with helper scripts
- GitLab CI/CD: GitLab CI/CD Integration — equivalent pipeline definitions
Official LabVIEW container images are released on Docker Hub and documented using GitHub Releases.
Release notes: https://github.com/ni/labview-for-containers/releases
Each GitHub Release corresponds to one Docker image tag published on Docker Hub.
| GitHub Release | Docker Image Tag |
|---|---|
v2025q3-linux |
nationalinstruments/labview:2025q3-linux |
v2025q3patch1-linux |
nationalinstruments/labview:2025q3patch1-linux |
See FAQs for common questions about LabVIEW containers, headless LabVIEW, LabVIEWCLI, and CI/CD integration.
If you have acquired a development license, you may deploy and use LabVIEW software within Docker containers, virtual machines, or similar containerized environments (“Container Instances”) solely for continuous integration, continuous deployment (CI/CD), automated testing, automated validation, automated review, automated build processes, static code analysis, unit testing, executable generation, and report generation activities. You may create unlimited Container Instances and run unlimited concurrent Container Instances for these authorized automation purposes. It is hereby clarified that You may only host, distribute, and make available Container Instances containing LabVIEW software internally within your organization where such Container Instances are not made available to anyone outside your organization unless otherwise agreed under your license terms. Container Instances may be accessed by multiple users within your organization for the automation purposes specified in this paragraph, without requiring individual licenses for each user accessing the Container Instance. In no event may you use LabVIEW software within Container Instances for development purposes, including but not limited to creating, editing, or modifying LabVIEW code, with the exception of debugging automation processes as specifically permitted above. You may not distribute Container Instances containing LabVIEW software to third parties outside your organization without NI’s prior written consent.
- Examples — interactive usage, LabVIEWCLI commands, and debugging
- CI/CD Examples — MassCompile and VI Analyzer workflows
- Headless LabVIEW — headless execution mode details