You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of testing #793 I was trying to build the images using podman instead of docker. While the core is hard coded to invoke docker if I create a symlink from docker to podman on my machine somewhere at the start of the path it should work ok, and indeed the docker build command that the installer generation process outputs seems to work standalone. Unclear whether this is something specific to my machine or with podman itself, but worthy of investigation to look for a resolution. It's acting as though the process is squashing my PATH somewhere along the line but it's not lcear where that might be happening.
> Task :jdk:suse:packageJdkSuse FAILED
Watching 7 directories to track changes
Caching disabled for task ':jdk:suse:packageJdkSuse' because:
Build cache is disabled
Task ':jdk:suse:packageJdkSuse' is not up-to-date because:
Task has failed previously.
Watching 6 directories to track changes
Starting process 'command 'docker''. Working directory: /var/home/sxa/git/openjdk-installer/linux/jdk/suse/src/main/packaging Command: docker build --no-cache -t adoptium-packages-linux-jdk-suse -f Dockerfile /var/home/sxa/git/openjdk-installer/linux/jdk/suse/src/main/packaging
Watching 7 directories to track changes
:jdk:suse:packageJdkSuse (Thread[Execution worker for ':',5,main]) completed. Took 0.007 secs.
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':jdk:suse:packageJdkSuse'.
> A problem occurred starting process 'command 'docker''
The text was updated successfully, but these errors were encountered:
As part of testing #793 I was trying to build the images using
podman
instead of docker. While the core is hard coded to invokedocker
if I create a symlink fromdocker
topodman
on my machine somewhere at the start of the path it should work ok, and indeed thedocker build
command that the installer generation process outputs seems to work standalone. Unclear whether this is something specific to my machine or with podman itself, but worthy of investigation to look for a resolution. It's acting as though the process is squashing myPATH
somewhere along the line but it's not lcear where that might be happening.The text was updated successfully, but these errors were encountered: