Skip to content

Latest commit

 

History

History
91 lines (80 loc) · 4.81 KB

1-04-Docker-Create.md

File metadata and controls

91 lines (80 loc) · 4.81 KB
Raw

Test 1-04 - Docker Create

Purpose:

To verify that docker create 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. Docker pull busybox
  3. Issue docker create busybox to the new VIC appliance
  4. Issue docker create -t -i busybox to the new VIC appliance
  5. Issue docker create --name test1 busybox to the new VIC appliance
  6. Issue docker create -v /var/log busybox ls /var/log to the new VIC appliance
  7. Issue docker start to the new VIC appliance
  8. Issue docker logs to the new VIC appliance
  9. Issue docker create -v test-named-vol:/testdir busybox
  10. Issue docker start
  11. Issue docker logs to grab the disk size of the volume
  12. Issue docker create -v /dir:/dir busybox
  13. Create a named volume
  14. Create a mongo container with the above named volume (mapped to an image volume path) and an anonymous volume
  15. Inspect the above container and obtain the HostConfig.Binds field
  16. Inspect the above container and obtain the Config.Volumes field
  17. Issue docker create busybox /bin/top to the new VIC appliance
  18. Issue docker create fakeimage to the new VIC appliance
  19. Issue docker create fakeImage to the new VIC appliance
  20. Issue docker create --name busy1 busybox /bin/top to the new VIC appliance
  21. Issue docker start busy1 to the new VIC appliance
  22. Issue docker create --link busy1:busy1 --name busy2 busybox ping -c2 busy1 to the new VIC appliance
  23. Issue docker start busy2 to the new VIC appliance
  24. Issue docker logs busy2 to the new VIC appliance
  25. Create a container, rm the container, then create another container
  26. Create a container directly without pulling the image first for an image that hasn't been pulled yet
  27. Create a container without specifying a command
  28. Create a container with a custom amount of CPUs
  29. Create a container with a custom amount of Memory in GB
  30. Create a container with a custom amount of Memory in MB
  31. Create a container with a custom amount of Memory in KB
  32. Create a container with a custom amount of Memory in Bytes
  33. Create a container using a rest api call without HostConfig in the form data
  34. Create a container, then check the vm display name in vsphere through govc
  35. Create a container, then check the vm Destroy_Task method is disabled in VC through govc
  36. Create two containers with the same name in parallel, then check that only one attempt is successful
  37. Remove the container from Step 32 by name and create another container with the same name

Expected Outcome:

  • Steps 3-7 should all return without error and printing the container ID on return
  • Step 8 should show that the contents of the containers /var/log matches the contents of the hosts /var/log
  • Steps 9, 10 and 11 should return without errors and should successfully create a new volume called test-named-vol with disk size 975.9M
  • Step 12 should return with the error message - Error response from daemon: vSphere Integrated Containers does not support mounting directories as a data volume.
  • Steps 13 and 14 should succeed
  • Step 15's and 16's output should contain the named volume created in Step 13
  • Step 18 should return with the error message - Error: image library/fakeimage not found
  • Step 19 should return with the error message - Error parsing reference: "fakeImage" is not a valid repository/tag
  • Step 22 should result in success and the busy2 container should exist
  • Step 24 should show that busy2 was able to successfully ping busy1 just using the linked name
  • Step 25 should result in success for all three parts
  • Step 26 should return without error
  • Step 27 should return with the following error message - Error response from daemon: No command specified
  • Steps 28-32 should return without error.
  • Step 33 should return without error.
  • Step 34 should show that the VM display name equals to containerName-containerShortID and datastore folder name equal to containerID
  • Step 35 should show that the VM Destroy_Task method is disabled in VC
  • Step 36 should have one container create process succeed and the other fail with an error
  • Step 37 should succeed

Possible Problems:

None

=======

Simple Creates Verifying Folder Path

Purpose:

Enforce that we are creating the cvm's under the folder which owns the VCH appliance itself.

Test Steps:

  1. Pull busybox
  2. Deploy 3 containers with identifiable names and check their folder paths.
  3. Remove the 3 containers.

expected outcome:

  • step 1 should complete with rc of 0.
  • step 2 should complete with rc of 0 for all containers. All checks for container folder pathing should succeed as well.
  • step 3 Should complete with rc of 0.