Contents

@announce-output
Feature: Running a sandbox
  Background:
    Given I successfully run `docker pull registry.tld/conjur-appliance-cuke-master:4.9-stable`
    # The extra containers will use the `alpine` image, so we need to pull it first on the
    # host to use the authenticated DockerHub connection. This avoids hitting DockerHub
    # rate limits.
    And I successfully run `docker pull alpine`

  Scenario: sandbox for 'example' project be started
    Given I successfully start a sandbox for "example" with arguments "-t 4.9-stable --no-pull"

  Scenario: sandbox for 'example' project be started linked to another container
    Given I start a container named "other_host"
    Then I successfully start a sandbox for "example" with arguments "-t 4.9-stable --no-pull --link other_host -c 'ping -c1 other_host'"

  Scenario: sandbox for 'example' project be started on a network other than the default
    Given I start a container named "other_host" on network "test-net"
    Then I successfully start a sandbox for "example" with arguments "-t 4.9-stable --no-pull --net test-net -c 'ping -c1 other_host'"

  Scenario: sandbox for 'example' project be started on a network other than the default with a host aliased
    Given I start a container named "another_host" on network "test-net"
    Then I successfully start a sandbox for "example" with arguments "-t 4.9-stable --no-pull --net test-net --link another_host:other_host -c 'ping -c1 other_host'"

Version data entries

1 entries across 1 versions & 1 rubygems

Version	Path
conjur-debify-2.0.0	features/sandbox.feature