cbcbe0da2e
Currently the rkt driver does not expose a DriverNetwork instance after starting the container, which means that address_mode = 'driver' does not work. To get the container network information, we can call `rkt status` on the UUID of the container and grab the container IP from there. For the port map, we need to grab the pod manifest as it will tell us which ports the container exposes. We then cross-reference the configured port name with the container port names, and use that to create a correct port mapping. To avoid doing a (bad) reimplementation of the appc schema(which rkt uses for its manifest) and rkt apis, we pull those in as vendored dependencies. The versions used are the same ones that rkt use in their glide dependency configuration for version 1.28.0.
26 lines
1.1 KiB
Go
26 lines
1.1 KiB
Go
// Copyright 2015 The appc 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
|
|
//
|
|
// http://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.
|
|
|
|
// Package schema provides definitions for the JSON schema of the different
|
|
// manifests in the App Container Specification. The manifests are canonically
|
|
// represented in their respective structs:
|
|
// - `ImageManifest`
|
|
// - `PodManifest`
|
|
//
|
|
// Validation is performed through serialization: if a blob of JSON data will
|
|
// unmarshal to one of the *Manifests, it is considered a valid implementation
|
|
// of the standard. Similarly, if a constructed *Manifest struct marshals
|
|
// successfully to JSON, it must be valid.
|
|
package schema
|