profile
viewpoint
Stefan Scherer StefanScherer @docker Erlangen, Germany https://stefanscherer.github.io Engineer @docker, Microsoft MVP, Retired Docker Captain

push eventStefanScherer/compose

dependabot-preview[bot]

commit sha 101ee1cd62ec0f4018a9c1ac46b7de8d71f98215

Bump idna from 2.5 to 2.8 Bumps [idna](https://github.com/kjd/idna) from 2.5 to 2.8. - [Release notes](https://github.com/kjd/idna/releases) - [Changelog](https://github.com/kjd/idna/blob/master/HISTORY.rst) - [Commits](https://github.com/kjd/idna/compare/v2.5...v2.8) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

Nicolas De Loof

commit sha 55c5c8e8ac35d8c069ec8dd2ebeb919e39efca41

Report image we can't pull and must be built Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>

view details

Christopher Crone

commit sha d6b5d324e2b08587c3e4b99ac456276bc4d8d5f7

Use Python3 for macOS build environment With the deprecation of Python 2 coming soon, explicitly use Python 3. Signed-off-by: Christopher Crone <christopher.crone@docker.com>

view details

Ulysses Souza

commit sha e82d38f33319943778bf4716526001606e900b0d

Merge pull request #7052 from ndeloof/pull_can_build Report image we can't pull and must be built

view details

Christopher Crone

commit sha fedc8f71adef0eb33f6697fb16c3c4f023f83617

Build single binary and folder format for macOS Previously we were overwriting the single binary with the folder format. Signed-off-by: Christopher Crone <christopher.crone@docker.com>

view details

Christopher Crone

commit sha 882034388245b2a852a90ac4d1ffaa5daa37f751

Stash all macOS build artifacts Signed-off-by: Christopher Crone <christopher.crone@docker.com>

view details

Christopher Crone

commit sha b7a675b1c047dcf53da0076e074271e2af8e4d00

Upload macOS folder format to bintray Signed-off-by: Christopher Crone <christopher.crone@docker.com>

view details

Ulysses Souza

commit sha 8ebd7f96f0d8af70d275da6b27f83a463a76b5c7

Merge pull request #7070 from docker/macos-folder-build Build fixes for macOS

view details

Ulysses Souza

commit sha d92e9beec1b405df52ff745d8128c72b5bc35833

"Bump 1.25.1-rc1" Signed-off-by: Ulysses Souza <ulysses.souza@docker.com>

view details

Ulysses Souza

commit sha a23f39127e8fdf359d9fab199fa5745066b80c8b

Merge pull request #7071 from docker/bump-1.25.1-rc1 Bump 1.25.1-rc1

view details

dependabot-preview[bot]

commit sha d32b9f95cae761a6cbc878d894ce40e901b73e6a

Bump pytest-cov from 2.5.1 to 2.8.1 Bumps [pytest-cov](https://github.com/pytest-dev/pytest-cov) from 2.5.1 to 2.8.1. - [Release notes](https://github.com/pytest-dev/pytest-cov/releases) - [Changelog](https://github.com/pytest-dev/pytest-cov/blob/master/CHANGELOG.rst) - [Commits](https://github.com/pytest-dev/pytest-cov/compare/v2.5.1...v2.8.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

dependabot-preview[bot]

commit sha 780a425c6079feba7a9a6ad2dc832e33eee2f47e

Bump flake8 from 3.5.0 to 3.7.9 Bumps [flake8](https://gitlab.com/pycqa/flake8) from 3.5.0 to 3.7.9. - [Release notes](https://gitlab.com/pycqa/flake8/tags) - [Commits](https://gitlab.com/pycqa/flake8/compare/3.5.0...3.7.9) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

dependabot-preview[bot]

commit sha e9220f45df07c1f884d5d496507778d2cd4a1687

Bump coverage from 4.4.2 to 4.5.4 Bumps [coverage](https://github.com/nedbat/coveragepy) from 4.4.2 to 4.5.4. - [Release notes](https://github.com/nedbat/coveragepy/releases) - [Changelog](https://github.com/nedbat/coveragepy/blob/master/CHANGES.rst) - [Commits](https://github.com/nedbat/coveragepy/compare/coverage-4.4.2...coverage-4.5.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

dependabot-preview[bot]

commit sha e6e9263260f92249ed4f71d9bf62cefc0d186e3d

Bump ddt from 1.2.0 to 1.2.2 Bumps [ddt](https://github.com/datadriventests/ddt) from 1.2.0 to 1.2.2. - [Release notes](https://github.com/datadriventests/ddt/releases) - [Commits](https://github.com/datadriventests/ddt/compare/1.2.0...1.2.2) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

dependabot-preview[bot]

commit sha 025002260bb9ac45353d97bc8fd2f493147ffe37

Bump colorama from 0.4.0 to 0.4.3 Bumps [colorama](https://github.com/tartley/colorama) from 0.4.0 to 0.4.3. - [Release notes](https://github.com/tartley/colorama/releases) - [Changelog](https://github.com/tartley/colorama/blob/master/CHANGELOG.rst) - [Commits](https://github.com/tartley/colorama/compare/0.4.0...0.4.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

Ulysses Souza

commit sha cba8ad474ca0b3b2af20c792cf3cb4d331524bde

Fix by adding an assert to make the comparison effective Signed-off-by: Ulysses Souza <ulyssessouza@gmail.com>

view details

Ulysses Souza

commit sha 37eb7a509b41e5f39cfb6506ebfdef0a59f02765

Decode APIError explanation to unicode before usage Signed-off-by: Ulysses Souza <ulyssessouza@gmail.com>

view details

Ulysses Souza

commit sha b572a1e2e076bd3ec0d05ae39de5b925d465fce9

Merge pull request #7121 from ulyssessouza/fix_binary_string_error_treatment Fix binary string error treatment

view details

Ulysses Souza

commit sha f70b8c9a538e0cf3b8a0abde4113f69af8972a45

Merge remote-tracking branch 'upstream/release' into bump-1.25.1

view details

Ulysses Souza

commit sha a82fef0722142ee37458db2682f89868acbe0d32

"Bump 1.25.1" Signed-off-by: Ulysses Souza <ulyssessouza@gmail.com>

view details

push time in 16 hours

issue commentStefanScherer/docker-cli-builder

Upload as nuget package

I haven‘t planned that. Could you explain why this would be easier? How would that look like? What advantage would that be to have only the Docker CLI compared to have eg. Docker Desktop installed?

Roemer

comment created time in 20 hours

created tagStefanScherer/choco-docker-compose

tag1.25.2

Chocolatey 'docker-compose' package

created time in a day

release StefanScherer/choco-docker-compose

1.25.2

released time in a day

delete branch StefanScherer/choco-docker-compose

delete branch : update-1.25.2

delete time in a day

push eventStefanScherer/choco-docker-compose

Stefan Scherer

commit sha cb492d230a529f25949bb261a06ab77f9e6f467f

Update docker-compose 1.25.2

view details

Stefan Scherer

commit sha 247acb2d8ba4bcd0a486abfa08e2570910e91ab8

Merge pull request #43 from StefanScherer/update-1.25.2 Update docker-compose 1.25.2

view details

push time in a day

push eventStefanScherer/choco-docker-compose

Stefan Scherer

commit sha cb492d230a529f25949bb261a06ab77f9e6f467f

Update docker-compose 1.25.2

view details

push time in a day

create barnchStefanScherer/choco-docker-compose

branch : update-1.25.2

created branch time in a day

Pull request review commentdocker/docker-ce-packaging

Fix image based build to address for upstream changes

 ARG BUILDTIME ARG PLATFORM ARG PRODUCT ARG DEFAULT_PRODUCT_LICENSE+ARG TINI_COMMIT

Do we need to pass in that argument somewhere with --build-arg TINI_COMMIT ?

thaJeztah

comment created time in 2 days

Pull request review commentdocker/docker-ce-packaging

Fix image based build to address for upstream changes

 ARG BUILDTIME ARG PLATFORM ARG PRODUCT ARG DEFAULT_PRODUCT_LICENSE+ARG TINI_COMMIT ENV VERSION ${VERSION} ENV GITCOMMIT ${GITCOMMIT} ENV BUILDTIME ${BUILDTIME} ENV PLATFORM ${PLATFORM} ENV PRODUCT ${PRODUCT} ENV DEFAULT_PRODUCT_LICENSE ${DEFAULT_PRODUCT_LICENSE}+ENV TINI_COMMIT ${TINI_COMMIT}+SHELL ["/bin/bash", "-c"] # TODO The way we set the version could easily be simplified not to depend on hack/...-RUN bash ./hack/make/.go-autogen-RUN go build -o /dockerd \-    -tags 'autogen apparmor seccomp selinux journald' \+RUN source ./hack/make/.go-autogen; \+    go build -o /sbin/dockerd \

This /sbin/dockerd will cause a problem in the last stage. There's a COPY --from in line 80 that uses /dockerd as source.

This lead to a next question, why are there two relatively similar Dockerfile.engine* files that we have to maintain?

At least we should use the same pathes in both Dockerfiles, so the COPY instruction must be updated.

thaJeztah

comment created time in 2 days

created tagStefanScherer/choco-docker-compose

tag1.25.1

Chocolatey 'docker-compose' package

created time in 4 days

release StefanScherer/choco-docker-compose

1.25.1

released time in 4 days

push eventStefanScherer/choco-docker-compose

Gusztáv Varga

commit sha b6f988f49b663bf5038851c0fd6eb6d45216b377

Update to version 1.25.1

view details

Stefan Scherer

commit sha 73a13ba8541fc87c16d731e13297a6c3c0f31aaf

Merge pull request #42 from gusztavvargadr/update-1.25.1 Update to version 1.25.1

view details

push time in 4 days

startedcanonical/multipass

started time in 4 days

issue commentStefanScherer/packer-windows

VirtualBox 6.1 renamed --clipboard to --clipboard-mode

Thank you. I’ll take a look when vagrant supports it and adjust the templates. What‘s your experience? No other issues?

aucampia

comment created time in 4 days

issue commentmicrosoft/WSL

WSL 2 should automatically release disk space back to the host OS

It's back alive, got the Ubuntu distro working again. Seem like I just have to wait a little bit. Terminal opens and I have the bash prompt. The WSL integration was disabled, after enabling again docker also works again in Ubuntu.

dsmaher

comment created time in 4 days

issue commentmicrosoft/WSL

WSL 2 should automatically release disk space back to the host OS

I've tried the commands as well. I could find an issue that docker engine (docker.sock) is not available after starting. But after restarting Docker Desktop and changing the settings / resources / wsl integration to off + apply, then to on again + apply did the trick. Looks like the sock

I ran the test a second time, but now my whole Ubuntu 18.04 distro is broken, the terminal closes either immediately or after some seconds without any text in it.

dsmaher

comment created time in 4 days

issue commenthashicorp/packer

Error in azure-arm packer elevated PowerShell provisioning

I've tried it with Packer 1.4.5, and this worked. Here is the log output.

<details> <summary>Click to expand!</summary>

14:10:19  ==> azure-arm: Waiting for WinRM to become available...
14:10:19  2020/01/17 13:10:12 packer: 2020/01/17 13:10:12 [INFO] Attempting WinRM connection...
14:10:19  2020/01/17 13:10:12 packer: 2020/01/17 13:10:12 [DEBUG] connecting to remote shell using WinRM
14:10:19  2020/01/17 13:10:19 packer: 2020/01/17 13:10:19 Checking that WinRM is connected with: 'powershell.exe -EncodedCommand aQBmACAAKABUAGUAcwB0AC0AUABhAHQAaAAgAHYAYQByAGkAYQBiAGwAZQA6AGcAbABvAGIAYQBsADoAUAByAG8AZwByAGUAcwBzAFAAcgBlAGYAZQByAGUAbgBjAGUAKQB7ACQAUAByAG8AZwByAGUAcwBzAFAAcgBlAGYAZQByAGUAbgBjAGUAPQAnAFMAaQBsAGUAbgB0AGwAeQBDAG8AbgB0AGkAbgB1AGUAJwB9ADsAIABlAGMAaABvACAAIgBXAGkAbgBSAE0AIABjAG8AbgBuAGUAYwB0AGUAZAAuACIA'
14:10:20  2020/01/17 13:10:19 packer: 2020/01/17 13:10:19 [INFO] starting remote command: powershell.exe -EncodedCommand aQBmACAAKABUAGUAcwB0AC0AUABhAHQAaAAgAHYAYQByAGkAYQBiAGwAZQA6AGcAbABvAGIAYQBsADoAUAByAG8AZwByAGUAcwBzAFAAcgBlAGYAZQByAGUAbgBjAGUAKQB7ACQAUAByAG8AZwByAGUAcwBzAFAAcgBlAGYAZQByAGUAbgBjAGUAPQAnAFMAaQBsAGUAbgB0AGwAeQBDAG8AbgB0AGkAbgB1AGUAJwB9ADsAIABlAGMAaABvACAAIgBXAGkAbgBSAE0AIABjAG8AbgBuAGUAYwB0AGUAZAAuACIA
14:10:28  ==> azure-arm: #< CLIXML
14:10:28      azure-arm: WinRM connected.
14:10:28  2020/01/17 13:10:28 packer: 2020/01/17 13:10:28 [INFO] command 'powershell.exe -EncodedCommand aQBmACAAKABUAGUAcwB0AC0AUABhAHQAaAAgAHYAYQByAGkAYQBiAGwAZQA6AGcAbABvAGIAYQBsADoAUAByAG8AZwByAGUAcwBzAFAAcgBlAGYAZQByAGUAbgBjAGUAKQB7ACQAUAByAG8AZwByAGUAcwBzAFAAcgBlAGYAZQByAGUAbgBjAGUAPQAnAFMAaQBsAGUAbgB0AGwAeQBDAG8AbgB0AGkAbgB1AGUAJwB9ADsAIABlAGMAaABvACAAIgBXAGkAbgBSAE0AIABjAG8AbgBuAGUAYwB0AGUAZAAuACIA' exited with code: 0
14:10:28  ==> azure-arm: <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="progress" RefId="0"><TN RefId="0"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj><Obj S="progress" RefId="1"><TNRef RefId="0" /><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj></Objs>
14:10:28  ==> azure-arm: Connected to WinRM!
14:10:28  2020/01/17 13:10:28 packer: 2020/01/17 13:10:28 Connected to machine
14:10:28  2020/01/17 13:10:28 packer: 2020/01/17 13:10:28 Error asking for input: no available tty
14:10:28  2020/01/17 13:10:28 packer: 2020/01/17 13:10:28 Running the provision hook
14:10:28  2020/01/17 13:10:28 [INFO] (telemetry) Starting provisioner powershell
14:10:28  2020/01/17 13:10:28 Error asking for input: no available tty
14:10:28  ==> azure-arm: Provisioning with Powershell...
14:10:28  ==> azure-arm: Provisioning with powershell script: win/scripts/ver.ps1
14:10:28  2020/01/17 13:10:28 packer: 2020/01/17 13:10:28 Opening win/scripts/ver.ps1 for reading
14:10:28  2020/01/17 13:10:28 packer: 2020/01/17 13:10:28 Uploading env vars to c:/Windows/Temp/packer-ps-env-vars-5e21b0c3-6305-227f-6f90-c0f31900a51a.ps1
14:10:28  2020/01/17 13:10:28 packer: 2020/01/17 13:10:28 [INFO] 74 bytes written for 'uploadData'
14:10:28  2020/01/17 13:10:28 [INFO] 74 bytes written for 'uploadData'
14:10:28  2020/01/17 13:10:28 packer: 2020/01/17 13:10:28 Uploading file to 'c:/Windows/Temp/packer-ps-env-vars-5e21b0c3-6305-227f-6f90-c0f31900a51a.ps1'
14:10:30  2020/01/17 13:10:30 packer: #< CLIXML
14:10:31  2020/01/17 13:10:31 packer: <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="progress" RefId="0"><TN RefId="0"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj></Objs>#< CLIXML
14:10:31  2020/01/17 13:10:31 packer: 2020/01/17 13:10:31 Building elevated command wrapper for: powershell -executionpolicy bypass "& { if (Test-Path variable:global:ProgressPreference){set-variable -name variable:global:ProgressPreference -value 'SilentlyContinue'};. c:/Windows/Temp/packer-ps-env-vars-5e21b0c3-6305-227f-6f90-c0f31900a51a.ps1; &'c:/Windows/Temp/script-5e21b0c3-f1f7-faa4-fcf3-40bf0946bd51.ps1'; exit $LastExitCode }"
14:10:31  2020/01/17 13:10:31 packer: 2020/01/17 13:10:31 Command [powershell -executionpolicy bypass "& { if (Test-Path variable:global:ProgressPreference){set-variable -name variable:global:ProgressPreference -value 'SilentlyContinue'};. c:/Windows/Temp/packer-ps-env-vars-5e21b0c3-6305-227f-6f90-c0f31900a51a.ps1; &'c:/Windows/Temp/script-5e21b0c3-f1f7-faa4-fcf3-40bf0946bd51.ps1'; exit $LastExitCode }" > %SYSTEMROOT%/Temp/packer-5e21b247-1a33-9bab-33bb-fa96e00b3404.out 2>&1] converted to [powershell -executionpolicy bypass &#34;&amp; { if (Test-Path variable:global:ProgressPreference){set-variable -name variable:global:ProgressPreference -value &#39;SilentlyContinue&#39;};. c:/Windows/Temp/packer-ps-env-vars-5e21b0c3-6305-227f-6f90-c0f31900a51a.ps1; &amp;&#39;c:/Windows/Temp/script-5e21b0c3-f1f7-faa4-fcf3-40bf0946bd51.ps1&#39;; exit $LastExitCode }&#34; &gt; %SYSTEMROOT%/Temp/packer-5e21b247-1a33-9bab-33bb-fa96e00b3404.out 2&gt;&amp;1] for use in XML string
14:10:31  2020/01/17 13:10:31 packer: 2020/01/17 13:10:31 Uploading elevated shell wrapper for command [powershell -executionpolicy bypass "& { if (Test-Path variable:global:ProgressPreference){set-variable -name variable:global:ProgressPreference -value 'SilentlyContinue'};. c:/Windows/Temp/packer-ps-env-vars-5e21b0c3-6305-227f-6f90-c0f31900a51a.ps1; &'c:/Windows/Temp/script-5e21b0c3-f1f7-faa4-fcf3-40bf0946bd51.ps1'; exit $LastExitCode }" > %SYSTEMROOT%/Temp/packer-5e21b247-1a33-9bab-33bb-fa96e00b3404.out 2>&1] to [C:/Windows/Temp/packer-elevated-shell-5e21b247-26af-84e0-4859-a486ccd7e854.ps1]
14:10:31  2020/01/17 13:10:31 packer: 2020/01/17 13:10:31 [INFO] 3230 bytes written for 'uploadData'
14:10:31  2020/01/17 13:10:31 [INFO] 3230 bytes written for 'uploadData'
14:10:31  2020/01/17 13:10:31 packer: <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="progress" RefId="0"><TN RefId="0"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj></Objs>2020/01/17 13:10:31 Uploading file to 'C:/Windows/Temp/packer-elevated-shell-5e21b247-26af-84e0-4859-a486ccd7e854.ps1'
14:10:34  2020/01/17 13:10:34 packer: #< CLIXML
14:10:35  2020/01/17 13:10:35 packer: <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="progress" RefId="0"><TN RefId="0"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj></Objs>#< CLIXML
14:10:35  2020/01/17 13:10:35 packer: 2020/01/17 13:10:35 [INFO] 1281 bytes written for 'uploadData'
14:10:35  2020/01/17 13:10:35 [INFO] 1281 bytes written for 'uploadData'
14:10:35  2020/01/17 13:10:35 packer: <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="progress" RefId="0"><TN RefId="0"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj></Objs>2020/01/17 13:10:35 Uploading file to 'c:/Windows/Temp/script-5e21b0c3-f1f7-faa4-fcf3-40bf0946bd51.ps1'
14:10:38  2020/01/17 13:10:37 packer: #< CLIXML
14:10:39  2020/01/17 13:10:39 packer: <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="progress" RefId="0"><TN RefId="0"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj></Objs>#< CLIXML
14:10:40  2020/01/17 13:10:39 packer: <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="progress" RefId="0"><TN RefId="0"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj></Objs>2020/01/17 13:10:39 [INFO] starting remote command: powershell -executionpolicy bypass -file "C:/Windows/Temp/packer-elevated-shell-5e21b247-26af-84e0-4859-a486ccd7e854.ps1"
14:10:42  2020/01/17 13:10:41 packer: 2020/01/17 13:10:41 [INFO] command 'powershell -executionpolicy bypass -file "C:/Windows/Temp/packer-elevated-shell-5e21b247-26af-84e0-4859-a486ccd7e854.ps1"' exited with code: 0
14:10:42  2020/01/17 13:10:41 packer: 2020/01/17 13:10:41 [INFO] RPC endpoint: Communicator ended with: 0
14:10:42  2020/01/17 13:10:41 [INFO] 82 bytes written for 'stdout'
14:10:42  2020/01/17 13:10:41 [INFO] 0 bytes written for 'stderr'
14:10:42  2020/01/17 13:10:41 [INFO] RPC client: Communicator ended with: 0
14:10:42  2020/01/17 13:10:41 [INFO] RPC endpoint: Communicator ended with: 0
14:10:42      azure-arm: The host OS is Windows Server Datacenter Server Core 1809, build 10.0.17763.973.
14:10:42  2020/01/17 13:10:41 packer: 2020/01/17 13:10:41 [INFO] 82 bytes written for 'stdout'
14:10:42  2020/01/17 13:10:41 packer: 2020/01/17 13:10:41 [INFO] 0 bytes written for 'stderr'
14:10:42  2020/01/17 13:10:41 packer: 2020/01/17 13:10:41 [INFO] RPC client: Communicator ended with: 0
14:10:42  2020/01/17 13:10:41 packer: 2020/01/17 13:10:41 c:/Windows/Temp/script-5e21b0c3-f1f7-faa4-fcf3-40bf0946bd51.ps1 returned with exit code 0

</details>

StefanScherer

comment created time in 4 days

issue openedhashicorp/packer

Error in azure-arm packer elevated PowerShell provisioning

Overview of the Issue

I have problems running an azure-arm packer build with PowerShell provision scripts. It works with Packer 1.4.0, fails with 1.5.1 and the nightly build 1.5.2-dev.

Reproduction Steps

Steps to reproduce this issue Run a packer build with azure-arm builder, the first provision script runs in elevated mode. I haven't tried to run a normal provision script yet.

Packer version

1.5.1 also tried 1.5.2 nightly from GitHub releases

Simplified Packer Buildfile

<details> <summary>Click to expand!</summary>

{
    "variables": {
        "docker_pkg_version": "19.03.5",
        "compose_pkg_version": "1.25.1",
        "cygwin_pkg_list": "openssh,vim,git,statgrab,jq,make",
        "fips_enabled": "0",
        "client_id": "secret",
        "client_secret": "secret",
        "tenant_id": "secret",
        "subscription_id": "secret",
        "rg": "",
        "name": "",
        "offer": "",
        "sku": "",
        "location": "West US",
        "isolation": "process",
        "packer_pkg_version": "",
        "qemu_img_pkg_version": "",
        "inspec_pkg_version": "",
        "inspec_profile": "test/jenkins-windows",
        "vm_size": "Standard_D4s_v3"
    },
    "builders": [
        {
            "type": "azure-arm",
            "client_id": "{{ user `client_id` }}",
            "client_secret": "{{ user `client_secret` }}",
            "tenant_id": "{{ user `tenant_id` }}",
            "subscription_id": "{{ user `subscription_id` }}",
            "managed_image_name": "{{ isotime \"2006-01-02-1504\" }}-{{ user `name` }}",
            "managed_image_resource_group_name": "{{ user `rg` }}",
            "managed_image_storage_account_type": "Standard_LRS",
            "os_type": "Windows",
            "image_publisher": "MicrosoftWindowsServer",
            "image_offer": "{{ user `offer` }}",
            "image_sku": "{{ user `sku` }}",
            "image_version": "{{ user `version` }}",
            "communicator": "winrm",
            "winrm_use_ssl": "true",
            "winrm_insecure": "true",
            "winrm_timeout": "30m",
            "winrm_username": "packer",
            "azure_tags": {
                "role": "jenkins-agent",
                "agent_type": "{{ user `name` }}",
                "project": "TAR-CICD-INFR"
            },
            "location": "{{ user `location` }}",
            "vm_size": "{{ user `vm_size` }}"
        }
    ],
    "provisioners": [
        {
            "elevated_user": "packer",
            "elevated_password": "{{.WinRMPassword}}",
            "type": "powershell",
            "scripts": [
                "win/scripts/ver.ps1",
                "win/scripts/install-cumulative-update.ps1"
            ]
        },
        {
            "type": "windows-restart",
            "restart_timeout": "45m"
        },
        {
            "type": "powershell",
            "scripts": [
                "win/scripts/ver.ps1",
                "win/scripts/features.ps1",
                "win/scripts/tcp-settings.ps1",
                "win/scripts/disable-defender.ps1",
                "win/scripts/disable-win-updates.ps1"
            ],
            "environment_vars": [
                "CHECK_WINDOWS_VERSION=1",
                "DOCKER_PKG_VERSION={{ user `docker_pkg_version` }}",
                "ISOLATION={{ user `isolation` }}"
            ]
        },
        {
            "type": "windows-restart"
        },
        {
            "type": "powershell",
            "scripts": [
                "win/scripts/fips.ps1",
                "win/scripts/setup.ps1"
            ],
            "environment_vars": [
                "DOCKER_PKG_VERSION={{ user `docker_pkg_version` }}",
                "COMPOSE_PKG_VERSION={{ user `compose_pkg_version` }}",
                "CYGWIN_PKG_LIST={{ user `cygwin_pkg_list`}}",
                "FIPS_ENABLED={{ user `fips_enabled` }}"
            ],
            "only": [
                "amazon-ebs"
            ]
        },
        {
            "type": "powershell",
            "scripts": [
                "win/scripts/install-docker.ps1",
                "win/scripts/install-compose.ps1",
                "win/scripts/java.ps1",
                "win/scripts/git.ps1",
                "win/scripts/make.ps1",
                "win/scripts/fips.ps1",
                "win/scripts/disable-ssh.ps1"
            ],
            "environment_vars": [
                "DOCKER_PKG_VERSION={{ user `docker_pkg_version` }}",
                "COMPOSE_PKG_VERSION={{ user `compose_pkg_version` }}",
                "FIPS_ENABLED={{ user `fips_enabled` }}"
            ],
            "only": [
                "azure-arm"
            ]
        },
        {
            "type": "inspec",
            "profile": "{{ user `inspec_profile` }}",
            "extra_arguments": [
                "--no-distinct-exit"
            ],
            "inspec_env_vars": [
                "FIPS_ENABLED={{ user `fips_enabled` }}",
                "DOCKER_PKG_VERSION={{ user `docker_pkg_version` }}",
                "COMPOSE_PKG_VERSION={{ user `compose_pkg_version` }}",
                "PACKER_PKG_VERSION={{ user `packer_pkg_version` }}",
                "QEMU_IMG_PKG_VERSION={{ user `qemu_img_pkg_version` }}",
                "INSPEC_PKG_VERSION={{ user `inspec_pkg_version` }}"
            ]
        },
        {
            "type": "powershell",
            "scripts": [
                "win/scripts/sysprep-azure.ps1"
            ]
        }
    ],
    "post-processors": [
        {
            "type": "manifest"
        }
    ]
}

</details>

My first provision script win/scripts/ver.ps1 looks like this:

<details> <summary>Click to expand!</summary>

$ProgressPreference = 'SilentlyContinue'
$ErrorActionPreference = 'Stop'

# fetch the current version number from host
$current=(Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion")
$currUBR=$current.UBR
$prefix="$($current.CurrentMajorVersionNumber).$($current.CurrentMinorVersionNumber).$($current.CurrentBuildNumber)."
Write-Output "The host OS is $($current.ProductName) $($current.InstallationType) $($current.ReleaseId), build $prefix$currUBR."

if ($env:CHECK_WINDOWS_VERSION) {
    Write-Output "Checking if host OS is up to date..."
    # fetch the tags from MCR, filter them with host version prefix, sort the update revisions and pick the highest
    $json=$(Invoke-WebRequest -UseBasicParsing https://mcr.microsoft.com/v2/windows/servercore/tags/list | ConvertFrom-Json)
    $hubUBR=($json.tags | Where-Object -FilterScript { $_.StartsWith($prefix) -and $_ -Match "^\d+\.\d+\.\d+\.\d+$" } |%{[System.Version]$_}|sort)[-1].Revision

    Write-Output "The host OS version is $prefix$currUBR, latest Windows Docker base image OS version is $prefix$hubUBR."

    if ($currUBR -lt $hubUBR) {
        Write-Error "Your host has update revision $currUBR, but should be updated to $hubUBR!"
    } else {
        Write-Output "The host is up to date."
    }
}

</details>

Operating system and Environment details

packer running from Ubuntu 18.04 amd64

Log Fragments and crash.log files

09:59:40  ==> azure-arm:  -> IP Address          : '104.45.228.5'
09:59:40  2020/01/17 08:59:30 packer_linux_amd64 plugin: Error asking for input: no available tty
09:59:40  2020/01/17 08:59:30 packer_linux_amd64 plugin: Waiting for WinRM, up to timeout: 30m0s
09:59:40  ==> azure-arm: Waiting for WinRM to become available...
09:59:40  2020/01/17 08:59:30 packer_linux_amd64 plugin: [INFO] Attempting WinRM connection...
09:59:40  2020/01/17 08:59:30 packer_linux_amd64 plugin: [DEBUG] connecting to remote shell using WinRM
09:59:40  2020/01/17 08:59:37 packer_linux_amd64 plugin: Checking that WinRM is connected with: 'powershell.exe -EncodedCommand aQBmACAAKABUAGUAcwB0AC0AUABhAHQAaAAgAHYAYQByAGkAYQBiAGwAZQA6AGcAbABvAGIAYQBsADoAUAByAG8AZwByAGUAcwBzAFAAcgBlAGYAZQByAGUAbgBjAGUAKQB7ACQAUAByAG8AZwByAGUAcwBzAFAAcgBlAGYAZQByAGUAbgBjAGUAPQAnAFMAaQBsAGUAbgB0AGwAeQBDAG8AbgB0AGkAbgB1AGUAJwB9ADsAIABlAGMAaABvACAAIgBXAGkAbgBSAE0AIABjAG8AbgBuAGUAYwB0AGUAZAAuACIA'
09:59:40  2020/01/17 08:59:38 packer_linux_amd64 plugin: [INFO] starting remote command: powershell.exe -EncodedCommand aQBmACAAKABUAGUAcwB0AC0AUABhAHQAaAAgAHYAYQByAGkAYQBiAGwAZQA6AGcAbABvAGIAYQBsADoAUAByAG8AZwByAGUAcwBzAFAAcgBlAGYAZQByAGUAbgBjAGUAKQB7ACQAUAByAG8AZwByAGUAcwBzAFAAcgBlAGYAZQByAGUAbgBjAGUAPQAnAFMAaQBsAGUAbgB0AGwAeQBDAG8AbgB0AGkAbgB1AGUAJwB9ADsAIABlAGMAaABvACAAIgBXAGkAbgBSAE0AIABjAG8AbgBuAGUAYwB0AGUAZAAuACIA
09:59:46  ==> azure-arm: #< CLIXML
09:59:46      azure-arm: WinRM connected.
09:59:46  2020/01/17 08:59:46 packer_linux_amd64 plugin: [INFO] command 'powershell.exe -EncodedCommand aQBmACAAKABUAGUAcwB0AC0AUABhAHQAaAAgAHYAYQByAGkAYQBiAGwAZQA6AGcAbABvAGIAYQBsADoAUAByAG8AZwByAGUAcwBzAFAAcgBlAGYAZQByAGUAbgBjAGUAKQB7ACQAUAByAG8AZwByAGUAcwBzAFAAcgBlAGYAZQByAGUAbgBjAGUAPQAnAFMAaQBsAGUAbgB0AGwAeQBDAG8AbgB0AGkAbgB1AGUAJwB9ADsAIABlAGMAaABvACAAIgBXAGkAbgBSAE0AIABjAG8AbgBuAGUAYwB0AGUAZAAuACIA' exited with code: 0
09:59:46  ==> azure-arm: <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="progress" RefId="0"><TN RefId="0"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj><Obj S="progress" RefId="1"><TNRef RefId="0" /><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj></Objs>
09:59:46  2020/01/17 08:59:46 packer_linux_amd64 plugin: Connected to machine
09:59:46  ==> azure-arm: Connected to WinRM!
09:59:46  2020/01/17 08:59:46 packer_linux_amd64 plugin: Error asking for input: no available tty
09:59:46  2020/01/17 08:59:46 packer_linux_amd64 plugin: Running the provision hook
09:59:46  2020/01/17 08:59:46 [INFO] (telemetry) Starting provisioner powershell
09:59:46  2020/01/17 08:59:46 Error asking for input: no available tty
09:59:46  ==> azure-arm: Provisioning with Powershell...
09:59:46  ==> azure-arm: Provisioning with powershell script: win/scripts/ver.ps1
09:59:46  2020/01/17 08:59:46 packer_linux_amd64 plugin: Opening win/scripts/ver.ps1 for reading
09:59:46  2020/01/17 08:59:46 packer_linux_amd64 plugin: Uploading env vars to c:/Windows/Temp/packer-ps-env-vars-5e21763d-cc44-cea6-0826-e7a6b3e94bd6.ps1
09:59:46  2020/01/17 08:59:46 packer_linux_amd64 plugin: [INFO] 74 bytes written for 'uploadData'
09:59:46  2020/01/17 08:59:46 [INFO] 74 bytes written for 'uploadData'
09:59:46  2020/01/17 08:59:46 packer_linux_amd64 plugin: Uploading file to 'c:/Windows/Temp/packer-ps-env-vars-5e21763d-cc44-cea6-0826-e7a6b3e94bd6.ps1'
09:59:48  2020/01/17 08:59:48 packer_linux_amd64 plugin: #< CLIXML
09:59:49  2020/01/17 08:59:49 packer_linux_amd64 plugin: <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="progress" RefId="0"><TN RefId="0"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj></Objs>#< CLIXML
09:59:49  2020/01/17 08:59:49 packer_linux_amd64 plugin: Building elevated command wrapper for: powershell -executionpolicy bypass "& { if (Test-Path variable:global:ProgressPreference){set-variable -name variable:global:ProgressPreference -value 'SilentlyContinue'};. c:/Windows/Temp/packer-ps-env-vars-5e21763d-cc44-cea6-0826-e7a6b3e94bd6.ps1; &'c:/Windows/Temp/script-5e21763d-9b3a-2948-6d3f-6f3d344d868b.ps1'; exit $LastExitCode }"
09:59:49  2020/01/17 08:59:49 packer_linux_amd64 plugin: Command [powershell -executionpolicy bypass "& { if (Test-Path variable:global:ProgressPreference){set-variable -name variable:global:ProgressPreference -value 'SilentlyContinue'};. c:/Windows/Temp/packer-ps-env-vars-5e21763d-cc44-cea6-0826-e7a6b3e94bd6.ps1; &'c:/Windows/Temp/script-5e21763d-9b3a-2948-6d3f-6f3d344d868b.ps1'; exit $LastExitCode }" > %SYSTEMROOT%/Temp/packer-5e217785-fb7f-a442-88d8-86520c890a36.out 2>&1] converted to [powershell -executionpolicy bypass &#34;&amp; { if (Test-Path variable:global:ProgressPreference){set-variable -name variable:global:ProgressPreference -value &#39;SilentlyContinue&#39;};. c:/Windows/Temp/packer-ps-env-vars-5e21763d-cc44-cea6-0826-e7a6b3e94bd6.ps1; &amp;&#39;c:/Windows/Temp/script-5e21763d-9b3a-2948-6d3f-6f3d344d868b.ps1&#39;; exit $LastExitCode }&#34; &gt; %SYSTEMROOT%/Temp/packer-5e217785-fb7f-a442-88d8-86520c890a36.out 2&gt;&amp;1] for use in XML string
09:59:49  2020/01/17 08:59:49 packer_linux_amd64 plugin: Uploading elevated shell wrapper for command [powershell -executionpolicy bypass "& { if (Test-Path variable:global:ProgressPreference){set-variable -name variable:global:ProgressPreference -value 'SilentlyContinue'};. c:/Windows/Temp/packer-ps-env-vars-5e21763d-cc44-cea6-0826-e7a6b3e94bd6.ps1; &'c:/Windows/Temp/script-5e21763d-9b3a-2948-6d3f-6f3d344d868b.ps1'; exit $LastExitCode }" > %SYSTEMROOT%/Temp/packer-5e217785-fb7f-a442-88d8-86520c890a36.out 2>&1] to [C:/Windows/Temp/packer-elevated-shell-5e217785-d4d4-7c72-d85a-0e6089798e8d.ps1]
09:59:49  2020/01/17 08:59:49 packer_linux_amd64 plugin: [INFO] 3198 bytes written for 'uploadData'
09:59:49  2020/01/17 08:59:49 [INFO] 3198 bytes written for 'uploadData'
09:59:49  2020/01/17 08:59:49 packer_linux_amd64 plugin: <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="progress" RefId="0"><TN RefId="0"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj></Objs>Uploading file to 'C:/Windows/Temp/packer-elevated-shell-5e217785-d4d4-7c72-d85a-0e6089798e8d.ps1'
09:59:56  2020/01/17 08:59:55 packer_linux_amd64 plugin: #< CLIXML
09:59:56  2020/01/17 08:59:56 packer_linux_amd64 plugin: <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="progress" RefId="0"><TN RefId="0"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj></Objs>#< CLIXML
09:59:56  2020/01/17 08:59:56 packer_linux_amd64 plugin: [INFO] 1281 bytes written for 'uploadData'
09:59:56  2020/01/17 08:59:56 [INFO] 1281 bytes written for 'uploadData'
09:59:56  2020/01/17 08:59:56 packer_linux_amd64 plugin: <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="progress" RefId="0"><TN RefId="0"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj></Objs>Uploading file to 'c:/Windows/Temp/script-5e21763d-9b3a-2948-6d3f-6f3d344d868b.ps1'
09:59:59  2020/01/17 08:59:59 packer_linux_amd64 plugin: #< CLIXML
10:00:00  2020/01/17 09:00:00 packer_linux_amd64 plugin: <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="progress" RefId="0"><TN RefId="0"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj></Objs>#< CLIXML
10:00:00  2020/01/17 09:00:00 packer_linux_amd64 plugin: <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"><Obj S="progress" RefId="0"><TN RefId="0"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64 N="SourceId">1</I64><PR N="Record"><AV>Preparing modules for first use.</AV><AI>0</AI><Nil /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> </SD></PR></MS></Obj></Objs>[INFO] starting remote command: powershell -executionpolicy bypass -file "C:/Windows/Temp/packer-elevated-shell-5e217785-d4d4-7c72-d85a-0e6089798e8d.ps1"
10:00:03  ==> azure-arm: (39,4):Task:
10:00:03  ==> azure-arm: At C:\Windows\Temp\packer-elevated-shell-5e217785-d4d4-7c72-d85a-0e6089798e8d.ps1:60 char:1
10:00:03  ==> azure-arm: + $f.RegisterTaskDefinition($name, $t, 6, "packer", $password, $logon_t ...
10:00:03  ==> azure-arm: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10:00:03  ==> azure-arm:     + CategoryInfo          : OperationStopped: (:) [], COMException
10:00:03  ==> azure-arm:     + FullyQualifiedErrorId : System.Runtime.InteropServices.COMException
10:00:03  ==> azure-arm:
10:00:03  ==> azure-arm: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
10:00:03  ==> azure-arm: At C:\Windows\Temp\packer-elevated-shell-5e217785-d4d4-7c72-d85a-0e6089798e8d.ps1:61 char:1
10:00:03  ==> azure-arm: + $t = $f.GetTask("\$name")
10:00:03  ==> azure-arm: + ~~~~~~~~~~~~~~~~~~~~~~~~~
10:00:03  ==> azure-arm:     + CategoryInfo          : OperationStopped: (:) [], FileNotFoundException
10:00:03  ==> azure-arm:     + FullyQualifiedErrorId : System.IO.FileNotFoundException
10:00:03  ==> azure-arm:
10:00:03  ==> azure-arm: Method invocation failed because [System.__ComObject] does not contain a method named 'Run'.
10:00:03  ==> azure-arm: At C:\Windows\Temp\packer-elevated-shell-5e217785-d4d4-7c72-d85a-0e6089798e8d.ps1:62 char:1
10:00:03  ==> azure-arm: + $t.Run($null) | Out-Null
10:00:03  ==> azure-arm: + ~~~~~~~~~~~~~~~~~~~~~~~~
10:00:03  ==> azure-arm:     + CategoryInfo          : InvalidOperation: (Run:String) [], RuntimeException
10:00:03  ==> azure-arm:     + FullyQualifiedErrorId : MethodNotFound
10:00:03  ==> azure-arm:

created time in 5 days

issue commentmoby/moby

Nightly binaries are outdated

I remember it has been stopped due to the bigger release pipeline refactoring. But I don't know more details which jobs has triggered that.

AkihiroSuda

comment created time in 6 days

issue commentmoby/moby

yum.dockerproject.org and apt.dockerproject.org are returning 403 errors

The docs how to install Docker can be found at https://docs.docker.com/install/linux/docker-ce/ubuntu/ or https://docs.docker.com/install/linux/docker-ce/centos/ Here you can find the current repo names.

rodrigc

comment created time in 7 days

delete branch StefanScherer/packer-windows

delete branch : win-2019

delete time in 7 days

push eventStefanScherer/packer-windows

Stefan Scherer

commit sha 27fd8899798fb4228c52af59729e9942b090d75f

Update Windows 2019 Eval ISO

view details

Stefan Scherer

commit sha 3c18ff1caac3514374d636b32a1b8d44474d86ff

Merge pull request #239 from StefanScherer/win-2019 Update Windows 2019 Eval ISO

view details

push time in 7 days

PR merged StefanScherer/packer-windows

Update Windows 2019 Eval ISO

Update Windows 2019 Eval ISO

+10 -10

0 comment

5 changed files

StefanScherer

pr closed time in 7 days

PR opened StefanScherer/packer-windows

Update Windows 2019 Eval ISO

Update Windows 2019 Eval ISO

+10 -10

0 comment

5 changed files

pr created time in 7 days

delete branch StefanScherer/packer-windows

delete branch : win-10-1909

delete time in 7 days

push eventStefanScherer/packer-windows

Stefan Scherer

commit sha 962bd5e9b98b8c3f5790f9913b8608c7a6331385

Update Windows 10 1909

view details

Stefan Scherer

commit sha bb56ab63a2af427f2799fd58abdcd541a1a88662

Merge pull request #238 from StefanScherer/win-10-1909 Update Windows 10 1909

view details

push time in 7 days

PR merged StefanScherer/packer-windows

Update Windows 10 1909

Update Windows 10 Enterprise Eval 1909 / 19h2

+2 -2

0 comment

1 changed file

StefanScherer

pr closed time in 7 days

create barnchStefanScherer/packer-windows

branch : win-2019

created branch time in 7 days

PR opened StefanScherer/packer-windows

Update Windows 10 1909

Update Windows 10 Enterprise Eval 1909 / 19h2

+2 -2

0 comment

1 changed file

pr created time in 7 days

create barnchStefanScherer/packer-windows

branch : win-10-1909

created branch time in 7 days

created tagStefanScherer/packer-windows

tag2020.01.15

Windows Templates for Packer: Win10, Server 2016, 1709, 1803, 1809, 2019, 1903, 1909, Insider with Docker

created time in 7 days

release StefanScherer/packer-windows

2020.01.15

released time in 7 days

push eventStefanScherer/packer-builder

Stefan Scherer

commit sha a6c015c2751170c5463f828b1085d6035324a599

Upload

view details

push time in 7 days

push eventStefanScherer/packer-builder

Stefan Scherer

commit sha ae4b3af7b9734d415482a248833494bde1e170a8

Build 10, 2019

view details

push time in 7 days

push eventStefanScherer/packer-builder

Stefan Scherer

commit sha c7bf7acd651d2faa2f8d9bbf87dff87b4b4bdb3f

Build 2019

view details

push time in 7 days

pull request commenthypriot/image-builder-rpi

Fix #288 Bluetooth MAC

Thanks @ProfFan Do you know if that works only with the built-in bluetooth, or also with USB bluetooth sticks eg on a Raspberry Pi 2?

If someone wants to test this, here is the SD card image with that change: https://246-49221370-gh.circle-artifacts.com/0/home/circleci/project/output/hypriotos-rpi-dirty.img.zip

ProfFan

comment created time in 7 days

pull request commentStefanScherer/windows-docker-machine

Add 2019-box-resized

Thank you. I haven‘t heard of vagrant-disksize, but it looks interesting. I‘m not sure if this PR will be merged, I don‘t want to force people to install additional vagrant plugins. But I‘ll think about it.

ianblenke

comment created time in 8 days

issue closedStefanScherer/windows-docker-machine

Having trouble adding box added after using vagrant

Based on the instructions, I have cloned the packer-windows repository and ran the commands:

vagrant box add windows_2019_docker windows_2019_docker_virtualbox.box --force

However, when navigating to the windows-docker-machine and attempting to run "vagrant up --provider virtualbox_dekstop windows_2019_docker", I get an error that machine does not exist for this environment.

Furthermore, when working a bit further, i went back to packer-windows folder, and ran "vagrant init windows_2019_docker" to add to the vagrantfile (maybe wrong repo), but when I instatiate it, i still do not see it under "docker context ls" command.

Instructions need some clarification for sure.

closed time in 8 days

rroman81

issue commenthypriot/image-builder-rpi

HypriotOS doesn't boot on raspberry pi 4B

Thanks for sharing the Pi4 firmware update @Duvel

MaartenKleijwegt

comment created time in 11 days

issue commentmicrosoft/WSL

[WSL2] Enabled WSL2 on old CPU, disable the "Virtual Machine Platform" feature?

@danielsballes No, I don't expect a solution to run WSL2 on old CPU's. I asked if the UI could grey out the check bot to let users install that feature that doesn't seem to work.

@Chaturanga42 Well, I just tried to use WSL2 to see edge cases during our development in Docker Desktop to support Windows 10 Home. Agreed, if you want to use WSL2 it's the end of these old CPUs.

StefanScherer

comment created time in 11 days

issue commentdocker/for-win

Allow install on Windows 10 Home 18945+ for desktop wsl2 tech preview

@josenobile Docker Desktop can start the engine automatically after login. The Docker CLI also works from the Windows terminals, if you want to try another distro you don't have to install Docker engine multiple times, ... No exact ETA, but watch out for the next Edge release.

LongLiveCHIEF

comment created time in 11 days

PR opened docker/app

Add Jenkins timeout

Signed-off-by: Stefan Scherer stefan.scherer@docker.com

- What I did

I've added a timeout to the Jenkins job, I saw https://ci.docker.com/teams-dsg/job/dsg/job/app/view/change-requests/job/PR-788/6/ running "forever".

- How I did it

- How to verify it

- Description for the changelog

- A picture of a cute animal (not mandatory)

+1 -0

0 comment

1 changed file

pr created time in 12 days

create barnchStefanScherer/app

branch : jenkins-timeout

created branch time in 12 days

push eventStefanScherer/app

Nick Adcock

commit sha c58a1721b7146a518b820e84d98aa630f8ece13f

Remove poll-breaking assertion in e2e test Removed assertion of local-in-docker command result when running e2e tests in swarm. This function is only used by the compatibility tests which does it's own assertion in a poll. The removed assertion was breaking the poll flow stopping the test from being able to retry. Signed-off-by: Nick Adcock <nick.adcock@docker.com>

view details

Silvin Lubecki

commit sha 31e76dfeb2ff2a75949f37ca2a452fb5fccead56

Merge pull request #784 from zappy-shu/add-logs-to-e2e-tests Remove poll-breaking assertion in e2e tests

view details

Ulysses Souza

commit sha df1c57ebd943834ce61420c10342925b8b783eed

Remove build time in binary Signed-off-by: Ulysses Souza <ulyssessouza@gmail.com>

view details

Nicolas De Loof

commit sha 3064a5da7fafd8ab3d4b776b22f3970719c00482

use docker/reference.Store to manage tags/digest by app image ID Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>

view details

Ulysses Souza

commit sha 15734917699e7d440cf97a504047858364398744

Use fork of buildx to fix file finalizer Signed-off-by: Ulysses Souza <ulyssessouza@gmail.com>

view details

ulyssessouza

commit sha 864442b8a77147390960e4fd5c17990907867cea

Use docker/buildx repo intead of a fork Signed-off-by: ulyssessouza <ulyssessouza@gmail.com>

view details

Silvin Lubecki

commit sha 6d698be254478dffe42cfc3b44664d8b611fd42f

Merge pull request #779 from ulyssessouza/refactor-build Bump buildx and fix file finalizer breaking the stdout fix

view details

push time in 12 days

issue commentdocker/for-win

Allow install on Windows 10 Home 18945+ for desktop wsl2 tech preview

@josenobile Nice, I understand you couldn't wait. :-) But please have in mind that Docker Desktop installer will support Windows 10 Home soon and bring docker CLI integration into WSL2 distros. That's our preferred way. If you give Docker Desktop (comes first with Edge version) please have in mind to uninstall docker again inside the WSL2 distro.

LongLiveCHIEF

comment created time in 12 days

delete branch StefanScherer/dockerfiles-windows

delete branch : test-chown

delete time in 13 days

push eventStefanScherer/dockerfiles-windows

Stefan Scherer

commit sha 25448db774927bb7a23e625c1afd9ec970697dc1

Test chown (#434)

view details

push time in 13 days

PR merged StefanScherer/dockerfiles-windows

Test COPY --chown

Test COPY -chown=user, doesn't work out of the box, add links to PR's and utility repo.

+19 -0

0 comment

4 changed files

StefanScherer

pr closed time in 13 days

push eventStefanScherer/dockerfiles-windows

Stefan Scherer

commit sha 02331d330119d8fc2829d69f4c496a0a1ff773c3

Test chown

view details

push time in 13 days

PR opened StefanScherer/dockerfiles-windows

Test COPY -chown

Test COPY -chown=user, doesn't work out of the box, add links to PR's and utility repo.

+19 -0

0 comment

4 changed files

pr created time in 13 days

create barnchStefanScherer/dockerfiles-windows

branch : test-chown

created branch time in 13 days

startednicholasdille/container-slides

started time in 13 days

delete branch hypriot/blog

delete branch : add-v1.12.0

delete time in 14 days

push eventhypriot/blog

Stefan Scherer

commit sha 1b53d730cade67ecbe263fa0e8f95e07f570be51

Add HypriotOS 1.12.0

view details

Stefan Scherer

commit sha c06e11341acd621960a09a812b9bae35e85e5767

Merge pull request #107 from hypriot/add-v1.12.0 Add HypriotOS 1.12.0

view details

push time in 14 days

PR merged hypriot/blog

Add HypriotOS 1.12.0
+1 -0

0 comment

1 changed file

StefanScherer

pr closed time in 14 days

issue commenthypriot/image-builder-rpi

wpa-supplicant regularly fails to initialize

Hello @altineller, which version do you use? I saw this problem from time to time. In my case I just unplugged power cable, plugged it in again (so the RPi booted a second time) and then WiFi just works without logging into it. I only have a screenshot from my error message. I'll add it here to track some progress to investigate the root cause.

rpi error message wpa_supplicant

wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
ifup: failed to bring up wlan0
altineller

comment created time in 14 days

PR opened hypriot/blog

Add HypriotOS 1.12.0
+1 -0

0 comment

1 changed file

pr created time in 14 days

create barnchhypriot/blog

branch : add-v1.12.0

created branch time in 14 days

delete branch hypriot/flash

delete branch : update-readme

delete time in 14 days

push eventhypriot/flash

Stefan Scherer

commit sha 3a53993670640edd324cdfe0bf9749cdfd00d2a0

Update README

view details

Stefan Scherer

commit sha 91311c54faa2ebc04e0dddba58b993a6a5319577

Merge pull request #163 from hypriot/update-readme Update README

view details

push time in 14 days

PR merged hypriot/flash

Update README
  • Remove text about flashing without an image, doesn't work with cloud-init
  • Add text about fake-hwclock.data file.
  • Update to flash 2.5.0
  • Update to HypriotOS 1.12.0

fixes #141

+10 -11

0 comment

1 changed file

StefanScherer

pr closed time in 14 days

issue closedhypriot/flash

Clarify usage without image

Both the readme and the usage state:

If no image is specified, the script will try to configure an existing image. This is useful to try several configuration without the need to rewrite the image every time.

However it is not at all clear how this works. Running ./flash -u user-data only prints the usage. I assume that this only works with specific options? If so, it would be nice if these are mentioned.

closed time in 14 days

Khartir

created taghypriot/image-builder-rpi

tagv1.12.0

SD card image for Raspberry Pi with Docker: HypriotOS

created time in 14 days

release hypriot/image-builder-rpi

v1.12.0

released time in 14 days

issue commentmoby/moby

NoSuchFileException issues when using process isolation

Correct, process isolation seems to work for the 1903 images on a 1909 windows 10 host. The official compatibility tables don't show this yet (https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility?tabs=windows-server-1909%2Cwindows-10-1909). I've looked into the other issue description, tested a bit with docker-compose and simple container images mounting folders. It's hard to tell where the problem is, but my guess if it's really not an application problem then it's something in windows itself.

@Barsonax Maybe you can investigate a bit more with sysinternals process monitor to see what happens in the containerized java process. With process isolation you can use process monitor on the host as described here: http://stefanscherer.github.io/find-dependencies-in-windows-containers/

Barsonax

comment created time in 15 days

delete branch hypriot/image-builder-rpi

delete branch : update-compose-1.25.1

delete time in 15 days

push eventhypriot/image-builder-rpi

Stefan Scherer

commit sha cca14aab0e6bb7b996a38936a26c0422aea055b1

Update docker-compose 1.25.1

view details

Stefan Scherer

commit sha 1114b95d1956c94959b40d6c5077dd8559b4a47d

Merge pull request #337 from hypriot/update-compose-1.25.1 Update docker-compose 1.25.1

view details

push time in 15 days

create barnchhypriot/image-builder-rpi

branch : update-compose-1.25.1

created branch time in 15 days

issue commentmicrosoft/WSL

Error using docker build in WSL 2

@InsulinShock At the moment we have this chapter in our docs https://docs.docker.com/docker-for-windows/wsl-tech-preview/

vadimdr

comment created time in 15 days

pull request commenthypriot/flash

Set date/time in cloud-init runcmd module as part on initial boot

@eloots oops, I forgot to prepend a v in the version tag, so it's 1.12.0-rc2 instead of v1.12.0-rc2 🤦‍♂

flash https://github.com/hypriot/image-builder-rpi/releases/download/1.12.0-rc2/hypriotos-rpi-1.12.0-rc2.img.zip
eloots

comment created time in 16 days

pull request commenthypriot/flash

Set date/time in cloud-init runcmd module as part on initial boot

@eloots You don‘t need a new option, the new flash v2.5.0 automatically looks if that file exists in the /boot partition after flashing and updates the timestamp. You do not need to create any file manually. The pre-release 1.12.0-rc2 has this file prepared. Older versions of HypriotOS don‘t support setting the timestamp this way, so creating the file wouldn‘t help.

eloots

comment created time in 16 days

issue commenthypriot/image-builder-rpi

Docker-compose not working on buster

There is a pre-release 1.12.0-rc2 right now where we could need some feedback.

Duvel

comment created time in 16 days

issue closedhypriot/flash

Need python2.7-dev libraries listed as a dependency

If you try to install sudo pip install awscli without Python headers, you'll get:

    ext/_yaml.c:4:20: fatal error: Python.h: No such file or directory
    compilation terminated.
    error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
    
    ----------------------------------------
Command "/usr/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-3U_5pa/PyYAML/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-xWNB69-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-3U_5pa/PyYAML/

So probably the following needs to be added:

sudo apt-get install python2.7-dev

closed time in 16 days

wsargent

issue closedhypriot/flash

Any chance to use PiBakery instead of flash?

Hi there I know there is allot of effort to flash and HypriotOS with very small amount of work.

But is it possible to flash HypriotOS also with the nice Tool PIBakery (master branch/2.0) ? Since 2.0 PiBakery also supports other images than Raspbian. https://github.com/davidferguson/pibakery

It would be nice if someone can give me a hint where to start? HypriotOS uses cloud-init. is it better to adapt something in HypriotOS to use PiBakery? or to write something in PiBakery to flash HypriotOS?

Thank you in advance for each suggestion...

closed time in 16 days

exocode

issue closedhypriot/flash

Set fake-hwclock to current date

Raspberry Pi only have a fake hwclock. It's used on boot and shutdown to get and save the "current" date. But the fake-hwclock is only updated while the Pi is running and so on first boot the date is usually very far in the past (the date when the image was created). To fix this, the fake-hwclock data file /etc/fake-hwclock.data should be updated when the image is flashed on the sd card. This will minimize the offset of the fake-hwclock on first boot.

This will most likely also fix hypriot/image-builder-rpi#304.

closed time in 16 days

Legion2

issue commenthypriot/flash

Set fake-hwclock to current date

Fixed with #162

Legion2

comment created time in 16 days

issue commenthypriot/flash

Avoiding default password (while also pre-configuring HypriotOS before flashing)

I finally had time to watch your Toorcon talk, thanks Katherine and you for your work you do to raise the awareness of this problem. Keep up the good work!

I remember when we introduced cloud-init I suggested to remove the default user at all, but as a team we decided against it to give users more convenience. Yes, we failed at "secure by default", but at least we have no users at all in the Linux partition. Only the boot partition has the user-data file that can be replace before the first boot.

If no user would be installed, more people could struggle (maybe Windows users that cannot use flash and use tools like Etcher) and would open GitHub issues that the card does not work, they cannot login etc. To reduce our effort in our spare time it was a consideration to leave that one default user in the user-data file. But users that know how to handle it can replace it before putting the SD card into the RPi for the first time. That were our ideas and the reason why we have the current constellation.

I'm not fully convinced if we should couple psec with flash, I fear this increases the installation requirements (have the right version Python, ...). It is an excellent idea to avoid default passwords, but I find it difficult

The challenge is the templating, replacing variables in the user-data file.

For me I solved it by putting the whole user-data file into pass password manager which is a command line tool. I once ran pass insert flash-wifi-yml and from time to time pass edit flash-wifi-yml. The user-data contains my own user, my SSH pub keys, my WiFi settings.

Then I have a small wrapper around flash tool, called flash-wifi.sh:

#!/bin/bash
pass flash-wifi-yml >/tmp/flash$$.yml
flash --userdata /tmp/flash$$.yml $*
rm -f /tmp/flash$$.yml

It takes the secret user-data file for the flash tool and removes it again from /tmp. Maybe not the best solution, but for my projects it's a good enough approach. I skipped the templating / variable expansion problem by completely replacing the user-data file with all my secrets.

With that flash-wifi.sh script I can use other parameters like --hostname/ -n to set the hostname on the fly. So that's convenient for me, but I haven't added pass into flash as well as it's my opinionated way to do it.

I would like to hear your suggestions how we could integrate psec (or other tools) to flash and/or our SD card images.

davedittrich

comment created time in 16 days

PR opened hypriot/flash

Update README
  • Remove text about flashing without an image, doesn't work with cloud-init
  • Add text about fake-hwclock.data file.
  • Update to flash 2.5.0
  • Update to HypriotOS 1.12.0

fixes #141

+10 -11

0 comment

1 changed file

pr created time in 16 days

create barnchhypriot/flash

branch : update-readme

created branch time in 16 days

issue closedhypriot/flash

Is it possible to create a /boot/cmdline.txt file?

I have a cloud-init setup I use to provision my Pis with and its working great. I want to get started with Kubernetes and I need to create a /boot/cmdline.txt file with the contents:

cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory

Is this possible using the cloud-init config and/or flash tool?

Thanks

closed time in 16 days

SteveEdson

issue closedhypriot/flash

flash is available through MacPorts

flash is now available through MacPorts:

$ sudo port sync
$ sudo port install flash

The curl and pv dependencies are installed by default. awscli is not and can be installed through:

$ sudo port install py37-awscli

closed time in 16 days

jrjsmrtn

PR closed hypriot/flash

Set date/time in cloud-init runcmd module as part on initial boot

As the Raspberry Pi's don't have a Real Time Clock (RTC), it takes a while before ntpd sets the time to the current (real) time. This creates a problem as apt-get update relies on the date/time being not too far off the mark. This commit will add a command as part of the runcmd section of cloud-init that sets the date/time to the date/time at which the ssd was flashed. Even though this will not set the date/time accurately, the skew is small enough to make apt-get update work.

+20 -0

39 comments

1 changed file

eloots

pr closed time in 16 days

pull request commenthypriot/flash

Set date/time in cloud-init runcmd module as part on initial boot

The new combo flash v2.5.0 and HypriotOS v1.12.0-rc2 solve this issue.

eloots

comment created time in 16 days

created taghypriot/flash

tag2.5.0

Command line script to flash SD card images of any kind

created time in 16 days

release hypriot/flash

2.5.0

released time in 16 days

delete branch hypriot/flash

delete branch : set-time

delete time in 16 days

push eventhypriot/flash

firecyberice

commit sha ad6507d87546e352422940554598a34bbb83c795

set fake-hwclock

view details

Stefan Scherer

commit sha 515c0c4f4ae5736e7953ba5ecda37939a389afe2

Fix date for macOS

view details

Stefan Scherer

commit sha 1ce3d5aedec49ed992707a10af9275cfb35c0714

Add test for fake-hwclock.data

view details

Stefan Scherer

commit sha 0e4ca4c2c368b263293a3cc8f2e8321d1c18f297

Merge pull request #162 from hypriot/set-time set fake-hwclock

view details

push time in 16 days

PR merged hypriot/flash

set fake-hwclock

Helper for hypriot/image-builder-rpi#334

+39 -1

0 comment

2 changed files

firecyberice

pr closed time in 16 days

Pull request review commenthypriot/flash

set fake-hwclock

+load test_helper+export OS=$(uname -s)++setup() {+  if [ ! -f fake-hwclock.img ]; then+    # download SD card image with cloud-init+    curl -L -o download.img.zip https://github.com/hypriot/image-builder-rpi/releases/download/1.12.0-rc2/hypriotos-rpi-1.12.0-rc2.img.zip+    unzip download.img.zip+    # cut only 70 MByte to flash faster+    dd if=hypriotos-rpi-1.12.0-rc2.img of=fake-hwclock.img bs=1048576 count=70+  fi+  stub_diskutil+}++teardown() {+  umount_sd_boot /tmp/boot+  rm -f $img+  unstub_diskutil+}++@test "fake-hwclock: flash updates fake-hwclock.data" {+  expected=$(TZ=UTC date '+%Y-%m-%d %H:%M')

Remove seconds from expected string here, this hopefully runs the tests stable enough in CI without a change in the minute.

firecyberice

comment created time in 16 days

push eventhypriot/flash

Stefan Scherer

commit sha 1ce3d5aedec49ed992707a10af9275cfb35c0714

Add test for fake-hwclock.data

view details

push time in 16 days

push eventhypriot/flash

Stefan Scherer

commit sha 515c0c4f4ae5736e7953ba5ecda37939a389afe2

Fix date for macOS

view details

push time in 16 days

created taghypriot/image-builder-rpi

tag1.12.0-rc2

SD card image for Raspberry Pi with Docker: HypriotOS

created time in 16 days

release hypriot/image-builder-rpi

1.12.0-rc2

released time in 16 days

issue closedhypriot/image-builder-rpi

Docker-compose not working on buster

I already found this with raspbian buster, but running docker-compose on hypriot 1.11 gives also the following error:

ImportError: No module named ssl_match_hostname

I found a solution here: https://github.com/docker/docker-py/issues/1502#issuecomment-506544849.

After doing it works for me:

sudo pip uninstall backports.ssl-match-hostname
sudo apt install python-backports.ssl-match-hostname

closed time in 16 days

Duvel
more