VM setup fails due to incorrect get-pip installation URL

[Scott Lederer]

I am unable to install this VM locally. This is blocking me from reviewing #134

Running ./scripts/setup results in the error message contained in this file.

I tried to address this by porting over fixes from other repos where we've encountered this problem. My attempt is captured in this branch: https://github.com/azavea/azavea-branding-guide/compare/fix/sml/pypa

Unfortunately it doesn't fix it – Ansible still generates ansible.docker and ansible.pip roles using the incorrect get-pip URL – and I don't know what to try next.

@azavea/operations

/cc @alexelash

[Terence Tuhinanshu]

I don't have access to this VM repo so can't push to your branch, but you were very close. To fix this, please use ansible-pip==2.0.1:

commit 6c1816cfc2d16ec07a6974574977da22a43c64d4
Author: Terence Tuhinanshu <[e-mail]>
Date:   Mon May 10 19:30:56 2021 -0400

    Fix get-pip URL in ansible-pip
    
    See https://github.com/azavea/ansible-pip/pull/19

diff --git a/deployment/ansible/roles.yml b/deployment/ansible/roles.yml
index 601543e..44a7521 100644
--- a/deployment/ansible/roles.yml
+++ b/deployment/ansible/roles.yml
@@ -1,6 +1,6 @@
 ---
 - src: azavea.pip
-  version: 2.0.0
+  version: 2.0.1
 
 - src: azavea.docker
   version: 4.0.0

See azavea/ansible-pip#19 for the actual fix in the module.

[Terence Tuhinanshu]

In addition, I kept getting this error whenever I ran update or server:

jekyll 3.7.3 | Error:  Too many levels of symbolic links @ rb_sysopen - /usr/src/app/deployment/ansible/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker/examples/roles/azavea.docker

I was able to get rid of this by ignoring the deployment directory within Docker:

diff --git a/docker-compose.yml b/docker-compose.yml
index f95d36d..413d6f6 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -6,6 +6,7 @@ services:
       dockerfile: Dockerfile
     volumes:
       - ./:/usr/src/app
+      - /usr/src/app/deployment
     environment:
       - JEKYLL_ENV=development
       - LANG=C.UTF-8

[Scott Lederer]

Thank you @rajadain, that worked! 🎉

Oddly enough, I'm not getting the "Too many levels" error. 😅

[Terence Tuhinanshu]

Ah in that case perhaps the second fix can be ignored for now, although it probably doesn't hurt to add it in either. I don't think the deployment folder is used from within the Docker container.