# PX4 Dev

PX4 Dev is a Docker container providing a complete, pre-configured development environment for PX4, the open-source autopilot stack for drones and unmanned vehicles. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/5985/px4-dev

## Description

px4-dev is a Docker container providing a complete, pre-configured development environment for PX4, the open-source autopilot stack for drones and unmanned vehicles. It bundles the full toolchain needed to build, simulate, and test PX4 firmware on your own computer, removing the time and complexity of installing each component manually. It suits hobbyists and developers who want to customise PX4 flight software without setting up a complex environment themselves.

## Platform availability

Available on 0 of 10 platforms.

## Health score

77/100 (Good), based on 3 of 4 factors.
- Maintained: 100 (last commit 16 days ago)
- Popular: 82 (12,972 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)

## Links

- Docker Hub: https://hub.docker.com/r/px4io/px4-dev
- Official website: https://px4.io
- GitHub: https://github.com/PX4/PX4-Autopilot
- Documentation: https://docs.px4.io

## Common questions

### What port and prerequisites are needed for the PX4 Docker simulation?

Docker must be installed and running. The provided Docker command starts a quick PX4 flight simulation and opens UDP port 14550 for MAVLink traffic.

### Can PX4 be customized for different vehicles or flight behavior?

Yes. The development guide covers supporting new vehicle types and variants, modifying flight algorithms, adding modes, integrating hardware, and communicating with PX4 from outside the flight controller.

### Where should PX4 problems and bug reports go?

Problems should first be posted on the support forum. The support page also covers diagnosing issues, reporting bugs, and the weekly dev call.

### Why can a custom PX4 build fail with a flash overflow?

The amount of code that can be loaded is limited by the board's flash memory. Adding modules or code can exceed that limit, causing a flash overflow even though the upstream version builds.

### What kinds of PX4 debugging and testing are covered in practitioner guides?

Guides cover Docker-based builds, sanitizer workflows, uXRCE-DDS session debugging, MAVLink signing analysis, and SITL integration testing.

---
Source: Our Local Host (https://ourlocalhost.com/app/5985/px4-dev), the self-hosted and open-source app directory.
