adoptium / adoptium/installer

`podman` doesn't seem to work as part of the installer generation process

Open
#794 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Jinja
Stars
168
Forks
77
Avg merge
2d 14h
Merged PRs (30d)
12

Description

As part of testing https://github.com/adoptium/installer/pull/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''
```

Contributor guide

Open the contributing guide

Research direction

Start with the :jdk:suse:packageJdkSuse task and the Dockerfile under linux/jdk/suse/src/main/packaging. Reproduce the generated `docker build` command using the reported docker-to-podman symlink, then inspect how the process receives PATH. Done means the installer generation task can invoke the container command successfully, or the podman-specific limitation is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.