kitchen-dockerwin 0.1.0 → 0.1.1

Sign up to get free protection for your applications and to get access to all the features.
Files changed (3) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +17 -3
  3. metadata +3 -3
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 70d765dc259c29987609209bcc304ffae6b10b7721c2ac291135ae8cc06d74f7
4
- data.tar.gz: a15bf7116dd11f270d34802a063027e9cffa0fcfc0ea69285be6ef017bf97ca0
3
+ metadata.gz: c3b313fb472cf7a3b8990f786fc57ef612119bd3915a760c80eec94d7f1d78c1
4
+ data.tar.gz: 73eea1c8cec0da5c67991fd808951b6aa8f9a69baacee3d5e87e7d548282f441
5
5
  SHA512:
6
- metadata.gz: 2dd91967432bea21103ff6b9084648d9bceb6941d98255ba160dba665bed78b6d263708de8eb18d546ee3a6088ff8081d2c4045a631e4992729584c33070df39
7
- data.tar.gz: 14b67db9875d72b10ef88ed2c9fc700f62ab0ff3ea462b0291e72e5e801bf3205e017d66f45649b40d771bbb4da1314605c99622580dffd2c81b85308948323e
6
+ metadata.gz: 4e309052f0887c708ac0164ae4fc1810aaea105e819dc1e6ee6b69fc5fd8f279b84504316f5591089bb6c8eecee0283d036141d08c0cd7972f117b8814d6e3e7
7
+ data.tar.gz: 0fe13ddb456d5cff73bccaaa5fc8db58a3311717c638b394956957017426de351384b789bee5ab98d170bbfe7643a96418c2e3f050452f4463320b7059728b8f
data/README.md CHANGED
@@ -8,13 +8,27 @@ An experimental Test Kitchen driver that supports Windows-based via Docker on a
8
8
 
9
9
  You'll need an environment with Docker for Windows installed, running and configured to run Windows Containers, and a working ChefDK installation (alternatively Ruby + Devkit + Test Kitchen gem).
10
10
 
11
- Whilst not necessary, the example shown assumes you have created your own Docker image with Chef Client inside.
11
+ ## Install the gem
12
12
 
13
- ## Example Dockerfile
13
+ ```
14
+ gem install kitchen-dockerwin
15
+ ```
16
+
17
+ If you are installing inside a Chef Workstation installation:
18
+
19
+ ```
20
+ chef gem install kitchen-dockerwin
21
+ ```
22
+
23
+ ## Dockerfile
24
+
25
+ Whilst not necessary, the example shown assumes you have created your own Docker image with Chef Client inside, this will dramatically speed up the testing process because the Chef Client will not need to be installed each time.
26
+
27
+ An example `Dockerfile` follows:
14
28
 
15
29
  ```
16
30
  FROM mcr.microsoft.com/windows/servercore:ltsc2019
17
- RUN ["powershell", "-executionpolicy unrestricted", "-noninteractive", "-command", ". { iwr -useb https://omnitruck.chef.io/install.ps1 } | iex; install; remove-item $env:TEMP\*.msi -force"]
31
+ RUN ["powershell", "-executionpolicy unrestricted", "-noninteractive", "-command", ". { iwr -useb https://omnitruck.chef.io/install.ps1 } | iex; install;"]
18
32
  ```
19
33
 
20
34
  Example command line to build image:
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: kitchen-dockerwin
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.0
4
+ version: 0.1.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Stuart Preston
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2019-05-19 00:00:00.000000000 Z
11
+ date: 2019-05-20 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: bundler
@@ -77,7 +77,7 @@ files:
77
77
  - README.md
78
78
  - lib/kitchen/driver/dockerwin.rb
79
79
  - lib/kitchen/transport/dockercli.rb
80
- homepage: https://github.com/stuartpreston/kitchen-windowscontainers
80
+ homepage: https://github.com/stuartpreston/kitchen-dockerwin
81
81
  licenses:
82
82
  - Apache-2.0
83
83
  metadata: {}