Openelis-analyzer-bridge compilation fialure

Good morning,

Running the latest develop branch code fails to build the Openelis analyzer bridge conatiner, see logs

Hi Ronald, thanks for bringing this up! I think the main issue might be our lack of a single clean and clear pathway for setting up OE2 + related services for local development. I’m working on a PR to make this much easier to do - let me know if you’re willing take a look at it and test things out!

Morning Piotr,

Thanks for looking into the issue. I am more than willing to test and provide feedback. Let me know when ready.

If you’d like to take a look: fix(dev): simplify source setup and isolated CI entrypoint by pmanko · Pull Request #4586 · DIGI-UW/OpenELIS-Global-2 · GitHub

1 Like

Hi Piotr,

Thanks for the soultion, I see that branch has been merged into development, I have pulled the lastest changes from develop. Running:
bash scripts/setup-workspace.sh
scripts/dev-stack up
scripts/dev-stack url

The container oe2-openelis-global-2-043601f8-dev-oe.openelis.org-1 is failing to start, attached is the container log file

[+] build 4/4
:check_mark: Image oe2-openelis-global-2-043601f8-dev-frontend:dev Built 62.9s
:check_mark: Image oe2-openelis-global-2-043601f8-dev-backend:dev Built 64.4s
:check_mark: Image oe2-openelis-global-2-043601f8-dev-analyzer-bridge:dev Built 61.9s
:check_mark: Image oe2-openelis-global-2-043601f8-dev-analyzer-mock:dev Built 65.9s
[+] up 7/8
:check_mark: Container oe2-openelis-global-2-043601f8-dev-frontend.openelis.org-1 Running 0.0s
:check_mark: Container oe2-openelis-global-2-043601f8-dev-db.openelis.org-1 Healthy 20.3s
:check_mark: Container oe2-openelis-global-2-043601f8-dev-openelis-analyzer-bridge-1 Running 0.0s
✘ Container oe2-openelis-global-2-043601f8-dev-oe.openelis.org-1 Error dependency oe.openelis.org fa… 20.9s
:check_mark: Container oe2-openelis-global-2-043601f8-dev-fhir.openelis.org-1 Healthy 20.3s
:check_mark: Container oe2-openelis-global-2-043601f8-dev-harness-catalog-init-1 Exited 18.4s
⠋ Container oe2-openelis-global-2-043601f8-dev-certs-1 Waiting 19.0s
:check_mark: Container oe2-openelis-global-2-043601f8-dev-astm-simulator-1 Started 15.8s
dependency failed to start: container oe2-openelis-global-2-043601f8-dev-oe.openelis.org-1 is unhealthy
dev-stack: Command ‘[‘docker’, ‘compose’, ‘-p’, ‘oe2-openelis-global-2-043601f8-dev’, ‘–project-directory’, ‘/home/ronald/OpenELIS-Global-2/projects/analyzer-harness’, ‘–env-file’, ‘/home/ronald/OpenELIS-Global-2/.env’, ‘-f’, ‘/home/ronald/OpenELIS-Global-2/projects/analyzer-harness/docker-compose.dev.yml’, ‘-f’, ‘/home/ronald/OpenELIS-Global-2/projects/analyzer-harness/docker-compose.base.yml’, ‘-f’, ‘/home/ronald/OpenELIS-Global-2/projects/analyzer-harness/docker-compose.analyzer-test.yml’, ‘-f’, ‘/home/ronald/OpenELIS-Global-2/projects/analyzer-harness/docker-compose.letsencrypt.yml’, ‘-f’, ‘/home/ronald/OpenELIS-Global-2/projects/analyzer-harness/docker-compose.worktree.yml’, ‘up’, ‘-d’, ‘–remove-orphans’]’ returned non-zero exit status 1.
ronald@tux:~/OpenELIS-Global-2$

Note: Every time I run scripts/dev-stack up all the containers are been rebuilt, is that the intended behaviour? I have limited Internet access and the

Hi @pmanko

The oe2-openelis-global-2-043601f8-dev-astm-simulator-1 container is constantly restarting and find below its logs

ronald@tux:~/OpenELIS-Global-2$ docker logs oe2-openelis-global-2-043601f8-dev-astm-simulator-1
exec /usr/local/bin/python: exec format error
exec /usr/local/bin/python: exec format error
exec /usr/local/bin/python: exec format error
exec /usr/local/bin/python: exec format error
exec /usr/local/bin/python: exec format error
exec /usr/local/bin/python: exec format error
exec /usr/local/bin/python: exec format error
exec /usr/local/bin/python: exec format error
exec /usr/local/bin/python: exec format error
exec /usr/local/bin/python: exec format error
exec /usr/local/bin/python: exec format error
exec /usr/local/bin/python: exec format error
exec /usr/local/bin/python: exec format error
exec /usr/local/bin/python: exec format error

@Ronald_Munjoma are you still blocked on this?