[bug]: docker setup.sh not compatible with podman-compose, and forges on regardless of errors

[ch604]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

when installing plane with podman on oracle linux 8, the flag "--policy" is not supported:

podman-compose: error: unrecognized arguments: --policy

detecting podman vs docker and skipping this flag in setup.sh would alleviate this problem.

[root@host5 plane]# which docker
alias docker='podman'
	/usr/bin/podman

while this specific example is not fatal, there are several other instances of flags which are not podman compatible, especially during the start phase:

KeyError: 'if_not_present'
Error: executing /usr/bin/podman-compose -f /opt/plane/plane-app/docker-compose.yaml --env-file=/opt/plane/plane-app/plane.env up -d --pull if_not_present --quiet-pull: exit status 1

the script errantly decides after this that the data migration was successful, and awaits the api to become available.

(the script also assumes that there are no other ports in use by other containers on the system, and attempts to take over port 80, though this is a different "bug". it should be advised inside the script to the user that the docker-compose and plane.env files should be adjusted as needed before attempting startup, though again, this is an unrelated suggestion.)

Steps to reproduce

1. deploy oracle linux 8 or another podman-based rhel variant
2. install podman, podman-docker, and podman-compose
3. download and run setup.sh as directed by the plane install documents, attempting to install and then start plane.

Environment

Production

Browser

None

Variant

Self-hosted

Version

v0.25.0

[mguptahub]

@ch604

Podman support is in our roadmap and will be coming in future release.