Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug]: Missing Live Services in Self-Host Build Process #6616

Open
1 task done
zxcv1884 opened this issue Feb 17, 2025 · 3 comments
Open
1 task done

[bug]: Missing Live Services in Self-Host Build Process #6616

zxcv1884 opened this issue Feb 17, 2025 · 3 comments
Assignees
Labels
🐛bug Something isn't working

Comments

@zxcv1884
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

I followed the install-community-edition method to self-host Plane on an amd64 machine. During ./setup install, it asked me to build the Plane Docker image on my local machine, and the build completed successfully. However, after running ./setup start, I noticed that the live services did not start.

Upon checking build.yml, it seems that the live services were not included in the build process.

Steps to reproduce

  1. Follow the install-community-edition instructions to self-host Plane on an amd64 machine.
  2. Run ./setup install and complete the build process.
  3. Run ./setup start.
  4. Observe that the live services are not running.

Environment

Production

Browser

None

Variant

Self-hosted

Version

v0.24.1

@zxcv1884 zxcv1884 added the 🐛bug Something isn't working label Feb 17, 2025
@akshat5302
Copy link
Collaborator

Hey @zxcv1884 could you please share the output of the cmds: uname -m uname
Also could you please share the screenshot of ./setup install command output, something like this

Image

@zxcv1884
Copy link
Author

$ uname -m
x86_64
$ uname
Linux
Image

@zxcv1884
Copy link
Author

These steps solved my issue:

I made the following changes in plane.env, and Plane was able to successfully pull the image from Docker Hub:

APP_RELEASE=stable
DOCKERHUB_USER=makeplane
CUSTOM_BUILD=false

However, during ./setup.sh install, I encountered the error:

unsupported manifest media type and no default available: application/vnd.oci.image.manifest.v1+json

This might be related to the Docker version. To resolve this, I commented out the following lines in setup.sh, and the installation proceeded successfully:

    # docker manifest inspect "${IMAGE_NAME}:${IMAGE_TAG}" | grep -q "\"architecture\": \"${CPU_ARCH}\"" &
    # local pid=$!
    # spinner "$pid"

    # echo "" >&2

    # wait "$pid"

    # if [ $? -eq 0 ]; then
        echo "Plane supports ${CPU_ARCH}" >&2
        echo "available"
        return 0
    # else
    #     echo "" >&2
    #     echo "" >&2
    #     echo "${UPPER_CPU_ARCH} images are not available for selected release ($APP_RELEASE)." >&2
    #     echo "" >&2
    #     echo "build"
    #     return 1
    # fi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants