Files

Loc Nguyen 513cebe7b7 VMware vSphere Integrated Containers provider (#206 )

* Add Virtual Kubelet provider for VIC

Initial virtual kubelet provider for VMware VIC.  This provider currently
handles creating and starting of a pod VM via the VIC portlayer and persona
server.  Image store handling via the VIC persona server.  This provider
currently requires the feature/wolfpack branch of VIC.

* Added pod stop and delete.  Also added node capacity.

Added the ability to stop and delete pod VMs via VIC.  Also retrieve
node capacity information from the VCH.

* Cleanup and readme file

Some file clean up and added a Readme.md markdown file for the VIC
provider.

* Cleaned up errors, added function comments, moved operation code

1. Cleaned up error handling.  Set standard for creating errors.
2. Added method prototype comments for all interface functions.
3. Moved PodCreator, PodStarter, PodStopper, and PodDeleter to a new folder.

* Add mocking code and unit tests for podcache, podcreator, and podstarter

Used the unit test framework used in VIC to handle assertions in the provider's
unit test.  Mocking code generated using OSS project mockery, which is compatible
with the testify assertion framework.

* Vendored packages for the VIC provider

Requires feature/wolfpack branch of VIC and a few specific commit sha of
projects used within VIC.

* Implementation of POD Stopper and Deleter unit tests (#4)

* Updated files for initial PR

2018-06-04 15:41:32 -07:00

1.6 KiB

Raw Blame History

Test 1-37 - Docker USER

Purpose:

To ensure that docker run -u and USER inside of a Dockerfile are respected on VIC.

References:

1 - Dockerfile Reference -- USER directive 2 - Docker command line reference (run options; look for --user)

Environment:

This test requires that a vSphere server is running and available

It also expects 3 Docker images exist, built from the Dockerfiles in vic/tests/resources/dockerfiles and published to a Docker image repository reachable by the machine running tests.

Test Steps:

Run a container that was built with a USER directive using a user created with RUN adduser
Run a container that specifies the user should have UID 2000 and doesn't specify GID
Run a container that does not specify a user and set it manually with docker run -u
Run a container that specifies UID 2000 and GID 2000
Run a container that does not specify a user or group but set them manually with docker run -u
Try to run a container with -u specifying a nonexistent user
Try to run a container with -u specifying a nonexistent group
Run a container specifying -u 0:0

Expected Outcome:

1-5 should run successfully with the options specified taking effect inside the container and reflected via id or whoami output 6 & 7 will fail with exit code 125 and an error message 8 will run successfully and whoami will report the user root

Possible Problems:

Docker image repository downtime or unreachability will cause failure on the tests that pull images from Docker Hub

1.6 KiB Raw Blame History