[bug]: Recent change to docker-compose-hub.yml is targeting non existent container label for plane-deploy

[larkinwc]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

It appears that a recent change to the docker-compose-hub.yml included a new container stored at makeplane/plane-deploy. I double checked and it looks like the only label currently on docker hub for that container is develop. This breaks being able to deploy without changing the target label to 'develop'.

Steps to reproduce

1. Checkout "master" (develop)
2. Follow self-hosting guide
3. When running docker compose -f docker-compose-hub.yml up the following error response is received from docker Error response from daemon: manifest for makeplane/plane-deploy:latest not found: manifest unknown: manifest unknown

Browser

Google Chrome

Version

Self-hosted

[henit-chobisa]

Hey @larkinwc, thanks for sharing the issue, Let have a look and get back to you. ✌🏼

[Doldge]

manually modifying the docker-compose-hub.yml file to point to the develop tag instead will allow you to proceed, however I still ended up with a fairly large pile of errors in the docker logs and a non-functional instance of Plane.

specifically:

• planedb and planebeatworker both spent a period erroring while waiting on the planebackend to apply migrations [seems like the the beatworker should be delayed from running until the migrations have finished].
• planefrontend erroring out on MODULE_NOT_FOUND
• planedeploy also erroring out on a MODULE_NOT_FOUND

[nsauter]

Anything new here?

[JowaDev]

I found a temporary solution, but unfortunately, it doesn't allow us to benefit from the latest release. You need to clone the GitHub repository with the following command:

git clone https://github.com/makeplane/plane.git plane

Then, switch to the commit of the previous release:

sudo git checkout 6f39771

Afterward, you can follow the basic instructions from the README.md file, such as:

chmod +x setup.sh
sudo ./setup.sh http://localhost

Next, execute the Docker Compose command for the self-hosted version:

sudo docker compose -f ./docker-compose-hub.yml up --build -d

Everything should work as expected...

[henit-chobisa]

Hey @larkinwc, @Doldge & @JowaDev, just wanted to let you know that we have resolved the above issue and have also introduced some new improvements, to make the self hosted experience, super smooth. The problem that you were facing above is because of the images not updating on dockerhub, which will be updated on our next release ( a few days ). I have mentioned the PRs that introduces the changes, you can have a look.
Again, thank you so much for your time. 🙏🏽

#2133
#2115
#2135

[hifnStudio]

This is gonna take time so it's good to stick with v0.11. If anyone updated to newest version and getting error then change config for 0.11

#2151 (comment)

You can copy provided config to go live with older version.

[larkinwc]

This is gonna take time so it's good to stick with v0.11. If anyone updated to newest version and getting error then change config for 0.11

#2151 (comment)

You can copy provided config to go live with older version.

Yes, there should be a separate issue filed to ensure that (the dockerfile in) versioned releases use image tags, since it looks like they currently do not.

[vihar]

We've implemented significant changes to enhance the stability of the self-hosted version. To address this issue, upgrade to the latest version. View documentation at https://docs.plane.so/self-hosting/. If you're still facing the issue, please let us know.