Start-Process : Cannot convert 'System.Object[]' to the type 'System.String' required by parameter 'RedirectStandardInput'. Specified method is not supported. At C:\Users\admin\Desktop\server.ps1:12 char:79 + ... -ArgumentList "/k" -RedirectStandardInput "\\.\pipe\${pipeName}", ` + ~~~~~~~~~~~~~~~~~~~~~~~~~

这个错误通常表示在使用 PowerShell 的 Start-Process 命令时，RedirectStandardInput 参数需要传入一个字符串，但你传入了一个对象数组。你需要将传入的参数转换为字符串类型。你可以尝试使用 -join 操作符将对象数组转换为字符串，例如：

$arguments = @("/k", "-someArgument")
$argumentsString = $arguments -join " "
Start-Process "cmd" -ArgumentList $argumentsString -RedirectStandardInput "\\.\pipe\${pipeName}" -Wait

这里使用 -join 操作符将 $arguments 数组中的元素合并为一个字符串，并将其赋值给 $argumentsString 变量。然后将 $argumentsString 变量传递给 Start-Process 命令的 -ArgumentList 参数。

相关问题

Cannot start service zookeeper: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/home/iot-master/kafka/zoo.cfg" to rootfs at "/opt/zookeeper-3.4.13/conf/zoo.cfg": mount /home/iot-master/kafka/zoo.cfg:/opt/zookeeper-3.4.13/conf/zoo.cfg (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

这个错误是由于在启动Zookeeper服务时，无法将本地文件系统路径/home/iot-master/kafka/zoo.cfg挂载到容器的/opt/zookeeper-3.4.13/conf/zoo.cfg目录。可能是由于指定的本地路径不存在或者是不是一个目录而导致的。

你可以尝试检查指定的本地路径/home/iot-master/kafka/zoo.cfg是否存在，并且确保它是一个文件而不是一个目录。同时，还需要确保指定的容器目录/opt/zookeeper-3.4.13/conf/zoo.cfg存在。

如果这些都没问题，可以尝试使用其他的本地路径或者容器目录来重新启动Zookeeper服务。

Could not resolve org.springframework.boot:spring-boot-gradle-plugin:3.0.6. Required by

This error message indicates that Gradle is unable to find the required version of the Spring Boot Gradle plugin (3.0.6) in any of its configured repositories.

To resolve this issue, you can try the following steps:

1. Make sure that you have specified the correct version of the plugin in your Gradle build file. Double-check the version number to ensure that it matches the version you need.

2. Check your internet connection and ensure that you can access the repository from which the required plugin is being downloaded. If you are behind a proxy, make sure that you have configured Gradle to use the correct proxy settings.

3. Try deleting the Gradle cache directory (located in your home directory under .gradle/caches/) and running the build again. Sometimes, Gradle cache can get corrupted and cause issues.

4. If none of the above steps work, try manually downloading the required plugin JAR file and placing it in your local Gradle repository. You can then refer to the plugin using the `mavenLocal()` repository in your Gradle build file.

I hope this helps!