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

Solution for Cannot create/start proxy container #54

Closed
mrrobot47 opened this Issue Jan 11, 2019 · 1 comment

Comments

3 participants
@mrrobot47
Copy link
Contributor

mrrobot47 commented Jan 11, 2019

Issues like: https://community.easyengine.io/t/cannot-create-start-proxy-container-please-make-sure-port-80-and-443-are-free-only-2-sites-are-on-server/11818 got reported after EasyEngine v4.0.8 update. Which switched to using global-services with docker-compose generated names post this update.

This issue is very specific on to docker-compose version 1.23.0 and 1.23.1, version 1.23.0 had a naming scheme update: the old scheme project>_<service>_<index> was updated to
<project>_<service>_<index>_<slug>, where <slug> is a randomly-generated
hexadecimal string.

This change is present for people who had installed EasyEngine between 31st October 2018 to 29th November 2018. Which crosses over with the time line of rc and stable release.

On 29th November this change was reverted back in docker-compose version 1.23.2.

A blogpost needs to written stating this issue and manual steps to resolve them need to be give. Due to this no existing sites got affected, only creation of new sites got hampered.

Steps to resolve this issue: (To be provided in blog for users):

  1. Update docker-compose to latest version.
sudo curl -L https://github.com/docker/compose/releases/download/1.23.2/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose
  1. Restart global-services:
cd /opt/easyengine/services && \
docker-compose down && \
docker-compose up -d 
  1. Restart sites:
for site in $(ee site list --format=text); do ee site disable $site && ee site enable $site; done

New site creation should start after this.

@kirtangajjar

This comment has been minimized.

v4 Maintenance Releases automation moved this from To Do to Done Jan 18, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment