d8dfun/virtual-kubelet
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity
Files
027b76651da0735fa84758d8d7928e336afaf791
virtual-kubelet/vendor/github.com/vmware/vic/tests/test-cases/Group1-Docker-Commands/1-12-Docker-RMI.md
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

2.0 KiB
Raw Blame History

Test 1-12 - Docker RMI

Purpose:

To verify that docker rmi command is supported by VIC appliance

References:

1 - Docker Command Line Reference

Environment:

This test requires that a vSphere server is running and available

Test Steps:

  1. Deploy VIC appliance to vSphere server
  2. Issue docker pull busybox to the VIC appliance
  3. Issue docker rmi busybox to the VIC appliance
  4. Issue docker pull busybox to the VIC appliance
  5. Issue docker create busybox /bin/top to the VIC appliance
  6. Issue docker rm to the VIC appliance
  7. Issue docker rmi busybox to the VIC appliance
  8. Issue docker pull busybox to the VIC appliance
  9. Issue docker create busybox /bin/top to the VIC appliance
  10. Issue docker rmi busybox to the VIC appliance
  11. Issue docker rmi -f busybox to the VIC appliance
  12. Issue docker rmi fakeImage to the VIC appliance
  13. Issue a docker pull by digest
  14. Issue a docker rmi by digest
  15. Issue docker pull for busybox and alpine
  16. Reboot the VCH and wait for it to initialize
  17. Obtain the image short ID for busybox
  18. Issue docker rmi using the short ID for busybox
  19. Obtain the image long ID for alpine
  20. Issue docker rmi using the long ID for alpine

Expected Outcome:

  • Step 3 and 7 should result in success and the image should be removed from inventory
  • Step 10 should result in failure and the error message below:
Failed to remove image (busybox): Error response from daemon: conflict: unable to remove repository reference "busybox" (must force) - container 6a26c7deb9b7 is using its referenced image 47bcc53f74dc
  • Step 11 should result in success and the image should be removed from inventory
  • Step 12 should result in an error with the following message:
Failed to remove image (fakeImage): Error response from daemon: No such image: fakeImage:latest
  • Steps 13-14 should result in success and the output of step 14 should contain the digest of the rmi'd image
  • Steps 15-20 should succeed

Possible Problems:

None