hashicorp / hashicorp/packer

'��' is not recognized as an internal or external command

Open
#12,556 6 comments 1 reaction 0 assignees View on GitHub
bug provisioner/windows-shell stage/needs-investigation stage/waiting-reply
Dominant language
Go
Stars
15.8k
Forks
3.3k
PR merge metrics
PR metrics pending

Description

Issue: '��' is not recognized as an internal or external command

This is happening in "type": "windows-shell" and it's inconsistent.. it may occur once on 10 times. This time it happened while trying to install nssm package.. and this looks like winrm communication problem.. I'm almost sure that nobody in this team gives a fuck about the issues (given the response time and how issues are automatically closed due to inactivity), but I will still try..

13:44:19 1691405058,,ui,message, amazon-ebs: C:\Users\vagrant>choco install octopusdeploy.tentacle -y
13:44:19 1691405059,,ui,message, amazon-ebs: Chocolatey v2.2.0
13:44:19 1691405059,,ui,message, amazon-ebs: Installing the following packages:
13:44:19 1691405059,,ui,message, amazon-ebs: octopusdeploy.tentacle
13:44:19 1691405059,,ui,message, amazon-ebs: By installing%!(PACKER_COMMA) you accept licenses for the packages.
13:44:21 1691405061,,ui,message, amazon-ebs: Progress: Downloading OctopusDeploy.Tentacle 7.0.68... 100%
13:44:21 1691405061,,ui,message, amazon-ebs:
13:44:21 1691405061,,ui,message, amazon-ebs: OctopusDeploy.Tentacle v7.0.68 [Approved]
13:44:21 1691405061,,ui,message, amazon-ebs: OctopusDeploy.Tentacle package files install completed. Performing other installation steps.
13:44:22 1691405062,,ui,message, amazon-ebs: Downloading OctopusDeploy.Tentacle 64 bit
13:44:22 1691405062,,ui,message, amazon-ebs: from 'https://download.octopusdeploy.com/octopus/Octopus.Tentacle.7.0.68-x64.msi'
13:44:22 1691405062,,ui,message, amazon-ebs: Progress: 100% - Completed download of C:\Users\vagrant\AppData\Local\Temp\chocolatey\OctopusDeploy.Tentacle\7.0.68\Octopus.Tentacle.7.0.68-x64.msi (7.19 MB).
13:44:22 1691405062,,ui,message, amazon-ebs: Download of Octopus.Tentacle.7.0.68-x64.msi (7.19 MB) completed.
13:44:26 1691405065,,ui,message, amazon-ebs: Hashes match.
13:44:26 1691405065,,ui,message, amazon-ebs: Installing OctopusDeploy.Tentacle...
13:44:30 1691405069,,ui,message, amazon-ebs: OctopusDeploy.Tentacle has been installed.
13:44:30 1691405069,,ui,message, amazon-ebs: OctopusDeploy.Tentacle may be able to be automatically uninstalled.
13:44:30 1691405069,,ui,message, amazon-ebs: The install of OctopusDeploy.Tentacle was successful.
13:44:30 1691405069,,ui,message, amazon-ebs: Software installed as 'msi'%!(PACKER_COMMA) install location is likely default.
13:44:30 1691405069,,ui,message, amazon-ebs:
13:44:30 1691405069,,ui,message, amazon-ebs: Chocolatey installed 1/1 packages.
13:44:30 1691405069,,ui,message, amazon-ebs: See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
13:44:30 1691405069,,ui,say,==> amazon-ebs: Provisioning with windows-shell...
13:44:30 1691405069,,ui,say,==> amazon-ebs: Provisioning with shell script: /var/tmp/windows-shell-provisioner1701371036
13:44:30 1691405070,,ui,message, amazon-ebs:
13:44:30 1691405070,,ui,error,==> amazon-ebs: '��' is not recognized as an internal or external command%!(PACKER_COMMA)
13:44:30 1691405070,,ui,message, amazon-ebs: C:\Users\vagrant>��
13:44:30 1691405070,,ui,error,==> amazon-ebs: operable program or batch file.
13:44:30 1691405070,,ui,say,==> amazon-ebs: Provisioning step had errors: Running the cleanup provisioner%!(PACKER_COMMA) if present...
13:44:30 1691405070,,ui,say,==> amazon-ebs: Terminating the source AWS instance...

{
"type": "windows-shell",
"inline": ["choco install octopusdeploy.tentacle -y"]
},
{
"type": "windows-shell",
"inline": ["choco install nssm -y"]
},

Using latest docker packer version - hashicorp/packer

Contributor guide

Open the contributing guide

Research direction

Start with the windows-shell provisioner and the two inline Chocolatey commands shown in the configuration. Reproduce the intermittent failure using the reported Docker Packer version and inspect the Windows/WinRM command path. Done means the inline command is transmitted without replacement characters and provisioning completes successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, docker
Domain
cloud, devops, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.