mirror of
https://github.com/apple/container.git
synced 2026-10-20 13:01:08 +00:00
- Closes #457. - A container can now declare additional DNS names for a network attachment with a repeatable `alias` property on `--network`, including subtree aliases that match every name below a domain. - With the default domain `test`, this container answers to `gateway.test` by its name, to `api.test` by the exact alias, and to `web.gateway.test`, `a.b.gateway.test` and every other name below `gateway.test` by the subtree alias. The motivating case is a gateway container in front of a local Kubernetes cluster that answers for `*.gateway.test`, with an ingress controller routing on the `Host` header. - An alias is an exact name, or a name with a leading dot that matches every name below it. A name without a dot gets the default domain, as container names do. A subtree alias must be below a name the same attachment owns, and exact names are unique across all containers, so a container cannot claim another container's namespace. The rules for one attachment are checked when a container is created, again when a stored container starts, and again by the network helper when it registers the aliases. See `docs/architecture/dns.md` for the design, the invariants and the security considerations.
126 lines
6.1 KiB
Swift
126 lines
6.1 KiB
Swift
//===----------------------------------------------------------------------===//
|
|
// Copyright © 2026 Apple Inc. and the container project authors.
|
|
//
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
// you may not use this file except in compliance with the License.
|
|
// You may obtain a copy of the License at
|
|
//
|
|
// https://www.apache.org/licenses/LICENSE-2.0
|
|
//
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
// See the License for the specific language governing permissions and
|
|
// limitations under the License.
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
import ContainerResource
|
|
import ContainerizationError
|
|
import DNSServer
|
|
|
|
/// Validates the DNS names that the network attachments of a new container claim.
|
|
///
|
|
/// A container claims the hostname of each attachment and the aliases it declares. Exact names must be
|
|
/// unique across all containers, whether they are running or stopped. A subtree alias such as
|
|
/// `.example.test` must be rooted at a name that the same attachment owns, so a container cannot claim
|
|
/// the part of the namespace below another container's name.
|
|
enum AttachmentNameValidator {
|
|
/// The most aliases that a single attachment may declare.
|
|
static let maximumAliasesPerAttachment = AliasPolicy.maximumAliasesPerAttachment
|
|
|
|
/// The fewest labels that an exact alias, or the base of a subtree alias, may have.
|
|
static let minimumAliasLabels = AliasPolicy.minimumLabels
|
|
|
|
/// Validates the attachments of a new container against the attachments of all existing containers.
|
|
///
|
|
/// Names are compared case-insensitively and without a trailing dot.
|
|
///
|
|
/// - Parameters:
|
|
/// - networks: The attachments of the container being created.
|
|
/// - existing: The attachments of every existing container.
|
|
/// - Throws: `ContainerizationError` with code `.exists` if a hostname or alias is already claimed,
|
|
/// and with code `.invalidArgument` if an alias is malformed or breaks a rule.
|
|
static func validate(networks: [AttachmentConfiguration], existing: [AttachmentConfiguration]) throws {
|
|
var claimed = Set<String>()
|
|
for attachment in existing {
|
|
claimed.insert(AttachmentOptions.canonicalHostname(attachment.options.hostname))
|
|
for alias in attachment.options.aliases {
|
|
claimed.insert(Self.canonicalAlias(alias))
|
|
}
|
|
}
|
|
|
|
var conflictingHostnames = [String]()
|
|
for attachment in networks where claimed.contains(AttachmentOptions.canonicalHostname(attachment.options.hostname)) {
|
|
conflictingHostnames.append(attachment.options.hostname)
|
|
}
|
|
guard conflictingHostnames.isEmpty else {
|
|
throw ContainerizationError(.exists, message: "hostname(s) already exist: \(conflictingHostnames)")
|
|
}
|
|
|
|
let ownHostnames = Set(networks.map { AttachmentOptions.canonicalHostname($0.options.hostname) })
|
|
var ownAliases = Set<String>()
|
|
var conflictingAliases = [String]()
|
|
for attachment in networks {
|
|
let aliases = attachment.options.aliases
|
|
guard !aliases.isEmpty else {
|
|
continue
|
|
}
|
|
|
|
// The rules that depend only on this attachment are shared with the network helper.
|
|
let rules: [DNSMatchRule]
|
|
do {
|
|
let hostname = try? DNSName(AttachmentOptions.canonicalHostname(attachment.options.hostname))
|
|
rules = try AliasPolicy.validate(aliases: aliases, hostname: hostname, network: attachment.network)
|
|
} catch let violation as AliasPolicy.Violation {
|
|
throw ContainerizationError(.invalidArgument, message: violation.description)
|
|
}
|
|
|
|
// The rules that involve the other attachments and the other containers.
|
|
for (alias, rule) in zip(aliases, rules) {
|
|
guard case .exact = rule else {
|
|
continue
|
|
}
|
|
let name = rule.description
|
|
guard !ownHostnames.contains(name) else {
|
|
throw ContainerizationError(.invalidArgument, message: "alias \"\(alias)\" is already a hostname of the container")
|
|
}
|
|
guard ownAliases.insert(name).inserted else {
|
|
throw ContainerizationError(.invalidArgument, message: "alias \"\(alias)\" is declared on more than one network")
|
|
}
|
|
if claimed.contains(name) {
|
|
conflictingAliases.append(alias)
|
|
}
|
|
}
|
|
}
|
|
guard conflictingAliases.isEmpty else {
|
|
throw ContainerizationError(.exists, message: "alias(es) already exist: \(conflictingAliases)")
|
|
}
|
|
}
|
|
|
|
/// Validates the attachments of a container that was read back from storage.
|
|
///
|
|
/// The stored configuration is not trusted to be what `validate` accepted when the container was
|
|
/// created, since the file can be damaged or edited. This checks every rule that does not depend on
|
|
/// other containers, so a stored container with bad names fails to start with an explanation.
|
|
///
|
|
/// - Throws: `ContainerizationError` with code `.invalidState` if the stored names break a rule.
|
|
static func validateStored(id: String, networks: [AttachmentConfiguration]) throws {
|
|
do {
|
|
try validate(networks: networks, existing: [])
|
|
} catch let error as ContainerizationError {
|
|
throw ContainerizationError(
|
|
.invalidState,
|
|
message: "the stored configuration of container \(id) has invalid network names: \(error)"
|
|
)
|
|
}
|
|
}
|
|
|
|
/// The normalized form of an alias that was stored with an existing container.
|
|
private static func canonicalAlias(_ alias: String) -> String {
|
|
guard let rule = try? DNSMatchRule(alias) else {
|
|
return AttachmentOptions.canonicalHostname(alias)
|
|
}
|
|
return rule.description
|
|
}
|
|
}
|