makeplane / plane

🔥 🔥 🔥 Open Source JIRA, Linear, Monday, and Asana Alternative. Plane helps you track your issues, epics, and product roadmaps in the simplest way possible.
http://plane.so
GNU Affero General Public License v3.0
30.24k stars 1.68k forks source link

[bug]: docker-compose.yaml validation error #5202

Closed gauravagnihotristla closed 2 weeks ago

gauravagnihotristla commented 3 months ago

Is there an existing issue for this?

Current behavior

fails to start validating /home///plane-selfhost/plane-app/docker-compose.yaml: services.worker.pull_policy services.worker.pull_policy must be one of the following: "always", "never", "if_not_present", "build", "missing"

Checking log file for Web and Space returns - service 'web'/'space' is not running

Steps to reproduce

Following the installation method from https://docs.plane.so/self-hosting/methods/docker-compose

Environment

Production

Browser

Google Chrome

Variant

Local

Version

v0.22-dev

ferdinandkeller commented 3 months ago

I am getting the same bug. Removing pull_policy from every single line in the docker compose file seems to work as a temporary fix.

blackat commented 3 months ago

Hello, got the same issue with Docker Compose 2.29.0:

# Not working
pull_policy: ${IMAGE_PULL_POLICY:-missing}

# Working
pull_policy: missing

Docker version

Client: Docker Engine - Community Version: 24.0.6 API version: 1.43 Go version: go1.20.7 Git commit: ed223bc Built: Mon Sep 4 12:32:12 2023 OS/Arch: linux/amd64 Context: default

Server: Docker Engine - Community Engine: Version: 24.0.6 API version: 1.43 (minimum version 1.12) Go version: go1.20.7 Git commit: 1a79695 Built: Mon Sep 4 12:32:12 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.24 GitCommit: 61f9fd88f79f081d64d6fa3bb1a0dc71ec870523 runc: Version: 1.1.9 GitCommit: v1.1.9-0-gccaecfc docker-init: Version: 0.19.0 GitCommit: de40ad0

blackat commented 3 months ago

Docker Compose version 2.29.1 seems solving the issue. I have updated and values are correctly interpolated now.

It seems a duplicated of the issue 12001, in 2.29.0.

mguptahub commented 3 months ago

this has been taken care in PR #5228

mguptahub commented 2 weeks ago

This has been resolved and released.