[jira] [Commented] (IGNITE-12007) Latest "apacheignite/web-console-backend" docker image is broken

["Evgenii Zhuravlev (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-12007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891744#comment-16891744 ] 

Evgenii Zhuravlev commented on IGNITE-12007:
--------------------------------------------

[~dpavlov] that's not the reason to close the ticket. This is the real issue and I see that users are facing it: https://stackoverflow.com/questions/57179602/starting-webagent-on-apache-ignite-for-docker

> Latest "apacheignite/web-console-backend" docker image is broken
> ----------------------------------------------------------------
>
>                 Key: IGNITE-12007
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12007
>             Project: Ignite
>          Issue Type: Bug
>          Components: UI
>    Affects Versions: 2.7
>            Reporter: Igor Belyakov
>            Priority: Critical
>
> It's not possible to run docker container by using the latest version of "apacheignite/web-console-backend" image.
> Next error happens on the start:
> {code:java}
> npm ERR! A complete log of this run can be found in:
> npm ERR! /root/.npm/_logs/2019-07-23T14_24_40_353Z-debug.log
> npm ERR! path /opt/web-console/package.json
> npm ERR! code ENOENT
> npm ERR! errno -2
> npm ERR! syscall open
> npm ERR! enoent ENOENT: no such file or directory, open '/opt/web-console/package.json'
> npm ERR! enoent This is related to npm not being able to find a file.
> npm ERR! enoent{code}
> How to reproduce:
> Run container by using docker-compose as described here: [https://hub.docker.com/r/apacheignite/web-console-backend]
>  
> Seems like it was broken by the next commit:
> [https://github.com/apache/ignite/commit/4c295f8f468ddfce458948c17c13b1748b13e918#diff-ec0d595d738c4207e08ce210624e902aR22]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)