Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.2.0, 1.2.1, 1.3.0
-
None
-
On an aarch64 Arm server, pull pre-build image from https://hub.docker.com/r/bigtop/slaves/tags/
Run:
$ sudo docker pull bigtop/slaves:trunk-debian-9-aarch64
$ sudo docker run -it --rm --workdir /ws -v `pwd`:/ws bigtop/slaves:trunk-debian-9-aarch64 bash -l
root@b40443df7cce:/ws#
- ./gradlew toolchain
- Error: Could not parse application options: invalid option: --parser
On an aarch64 Arm server, pull pre-build image from https://hub.docker.com/r/bigtop/slaves/tags/ Run: $ sudo docker pull bigtop/slaves:trunk-debian-9-aarch64 $ sudo docker run -it --rm --workdir /ws -v `pwd`:/ws bigtop/slaves:trunk-debian-9-aarch64 bash -l root@b40443df7cce:/ws# ./gradlew toolchain Error: Could not parse application options: invalid option: --parser
Description
This issue happens when building target for Debian-9.
Starting from puppet 4.x, --parse is not a valid option for puppet any more. This results in when running in pre-built image bigtop/slaves:trunk-debian-9-aarch64 (and trunk-debian-9), we met this error:
$ sudo docker run -it --rm --workdir /ws -v `pwd`:/ws bigtop/slaves:trunk-debian-9-aarch64 bash -l
root@b40443df7cce:/ws#
- ./gradlew toolchain
- Error: Could not parse application options: invalid option: --parser
root@b40443df7cce:/ws# puppet --version
4.8.2
BTW, using pre-built trunk-ubuntu-16.04 doesn't have this issue. Because it's puppetized to version 3.8.5.