v0.1.2 docker image from master not working

[rogelio-telnyx]

Hello, we're trying to run the latest docker master image, but we're getting this error and then the container stops:

# docker run sipcapture/homer-view:master
Cannot match against 'undefined' or 'null'

If we change to the latest image (version 0.1.1) it works fine, any ideas what can be causing this?
Thanks.

[lmangani]

Hi @rogelio-telnyx have you tried building a local image? I'll try replicate this deeper

[lmangani]

FYI Just pushed a new version from CI to test with

[rogelio-telnyx]

@lmangani are there any updates on this issue?

[lmangani]

@rogelio-telnyx have you tried using the latest images? There were no comments to my update on Oct 18th - just to be sure this is still the case. We also suggest you build your own images using the Dockerfiles included in the repository for consistency.

[rogelio-telnyx]

@lmangani we tried with the official docker image and also building it from sources using the master branch from October 8th. On both cases we get the same error: Cannot match against 'undefined' or 'null'
Are we missing an env variable?

[lmangani]

Are you launching it with a config file? See example here: https://github.com/sipcapture/homer-view-react/blob/master/example/docker-compose.yml

[enzoqtvf]

Hi @lmangani I was able to clearly reproduce the issue (I've been testing using a specific config file, but I don't think the issue is coming from there since it was working for us before)
Here is what I think is breaking the docker image when we are running it : 1752240

I've been making 2 branches to show that:

• https://github.com/enzoqtvf/homer-view-react/tree/docker-image-master-not-working from that one you can test that it's not working, I've just added a Makefile to make it simpler, simply run (eventually need to use sudo based on your docker config):

• make build

• make run -> you will see the error @rogelio-telnyx and I are talking about

• https://github.com/enzoqtvf/homer-view-react/tree/docker-image-master-working on this one I reverted the commit that is causing issues, and you can test that it works the same way:

  • make build
  • make run -> should run without an issue

Let me know if I should be more specific there

cc @rogelio-telnyx

[lmangani]

Thanks @enzoqtvf this would explain a lot. Let's roll it back and investigate in parallel.

[enzoqtvf]

Sounds good ! Thanks a lot @lmangani

[lmangani]

Done - FYI to explain why the testing was not matching, deleting the existing package-lock should really have the same effect as the requirement is indeed, correct and that's how this is currently tested.

Let me know if we're out of the woods!

[enzoqtvf]

Looking good, we can now build the image and run it :)
Thank you @lmangani !

[rogelio-telnyx]

@lmangani we can now run it but it looks just like v0.1.1, without any of the expected changes for v0.1.2, can you please confirm?