Docker and Swift: Containerizing Applications for iOS and macOS

Online Python Trainer for Beginners

Learn Python easily without overwhelming theory. Solve practical tasks with automatic checking, get hints in Russian, and write code directly in your browser — no installation required.

Start Course

Introduction to Docker and Swift: Why Does It Matter?

In modern software development, containerization has become the de facto standard for ensuring reproducibility, scalability, and ease of application deployment. If you develop with Swift for iOS or macOS, you are likely accustomed to the Xcode and Package Manager ecosystem. However, when it comes to server-side development (Swift on Server) or creating isolated environments for building and testing, Docker becomes an indispensable tool.

In this article, we will break down how to containerize Swift applications using Docker. You will learn how to create a Dockerfile for Swift, configure the environment for the server framework Vapor, and optimize the build process. This material will be useful both for iOS developers exploring backend development and for DevOps engineers working with Swift.

Docker Basics for a Swift Developer

Docker allows you to package an application along with all its dependencies into a lightweight container. This is especially relevant for Swift, as the compiler and libraries can vary depending on the OS version. Instead of manually configuring a server, you simply run a container.

Installing Docker and Swift SDK

First, make sure you have Docker installed. Then you will need a Swift image. The official image from Apple is available on Docker Hub:

docker pull swift:5.9

This image includes the Swift compiler, Package Manager, and basic utilities. You can use it both for building and running applications.

Creating a Simple Swift Application

Let's create a minimal console application:

// main.swiftprint("Hello, Docker with Swift!")

Initialize the project:

mkdir MySwiftApp && cd MySwiftAppswift package init --type executable

Writing a Dockerfile for Swift

Now let's create a Dockerfile in the project root. It is important to use a multi-stage build so that the final image is minimal.

# First stage: buildFROM swift:5.9 AS buildWORKDIR /appCOPY Package.swift Package.resolved ./RUN swift package resolveCOPY . .RUN swift build -c release --static-swift-stdlib

# Second stage: runFROM ubuntu:22.04WORKDIR /appCOPY --from=build /app/.build/release/MySwiftApp .CMD ["./MySwiftApp"]

Explanation:

--static-swift-stdlib — static linking of the Swift standard library, so you don't have to drag libswift.so into the image.
COPY Package.swift separately — caching dependencies by Docker.
Ubuntu 22.04 — a lightweight base for the runtime.

Build and run:

docker build -t my-swift-app .docker run --rm my-swift-app

Containerizing a Vapor Application

The Vapor framework is the most popular choice for server-side Swift. Let's look at a Dockerfile for a typical Vapor project.

Vapor Project Structure

Assume you have a project created via vapor new MyVaporApp. The Dockerfile will be more complex, as it needs to account for network and database interaction.

# Build stageFROM swift:5.9 AS buildRUN apt-get update && apt-get install -y libsqlite3-devWORKDIR /appCOPY Package.swift Package.resolved ./RUN swift package resolveCOPY . .RUN swift build -c release

# Run stageFROM swift:5.9-slimWORKDIR /appCOPY --from=build /app/.build/release/MyVaporApp .COPY --from=build /app/Public ./PublicCOPY --from=build /app/Resources ./ResourcesEXPOSE 8080CMD ["./MyVaporApp", "serve", "--hostname", "0.0.0.0", "--port", "8080"]

Important points: