Cross-platform development keeps software, container images, and delivery workflows usable across operating systems and processor architectures. Plan for platform changes early, even when current deployments need only one variant. section 12.5 section 16.2
Make Dockerfiles easier to move between platforms with these rules:
- Use multi-platform images in every FROM instruction. section 12.5
- Avoid operating-system-specific commands in RUN and CMD instructions. section 12.5
- Put complex startup or deployment logic in a cross-platform utility, or install a cross-platform shell such as PowerShell. section 12.5
- Choose base images and build services that cover the operating systems and architectures you actually need. section 12.5
A two-platform staging pipeline
A PowerShell build script can produce Linux images on Linux and Windows images on Windows. GitHub Actions runs separate Linux and Windows workflows: the Windows run starts only after Linux succeeds, then both publish staging images with platform-specific tags. section 16.2
Figure 12.15 Projects typically launch with Linux Intel support and add variants as they become popular.
Trace how a project can begin with Linux Intel support and add platform variants as users, developers, or operating costs create demand. section 12.5
