Re: Docker deployment with EXTERNAL_LIBS environment variable

2018-04-18 Thread Dmitry Pavlov
Hi Petr,

I've mentioned you in the ticket. Is it obvious change so we could apply
patch?

Or could you advise maintainer/expert here?

Sincerely,
Dmitriy Pavlov

ср, 18 апр. 2018 г. в 7:27, Roman Shtykh :

> I had the same problem (pretty common not having -i option) and fixed it.
> Need a review.
> https://issues.apache.org/jira/browse/IGNITE-8143
>
> -- Roman
>
>
> On Tuesday, April 17, 2018, 7:15:25 p.m. GMT+9, Petr Ivanov <
> mr.wei...@gmail.com> wrote:
>
>
> Hi, Kseniya.
>
>
> I guess that something wrong with wget in distribution (alpine-linux). I
> will need some testing to investigate further.
>
>
>
> > On 17 Apr 2018, at 13:02, Ksenia Vazhdaeva 
> wrote:
> >
> > Hello,
> >
> > I am trying to deploy Apache Ignite 2.4.0 in docker using external libs
> as
> > described at https://apacheignite.readme.io/docs/docker-deployment
> >
> > /docker run -d --name ignite -v
> >
> /storage/ignite/ignite-server-config.xml:/etc/ignite/ignite-server-config.xml
> > \
> >-e "CONFIG_URI=file:///etc/ignite/ignite-server-config.xml" -p
> > 47500:47500 \
> >-e
> > "EXTERNAL_LIBS=
> http://central.maven.org/maven2/org/apache/ignite/ignite-schedule/1.0.0/ignite-schedule-1.0.0.jar
> "
> > \
> >apacheignite/ignite:2.4.0/
> >
> > Docker container is started but in docker logs there is an error
> >
> > /wget: unrecognized option: i
> > BusyBox v1.27.2 (2017-12-12 10:41:50 GMT) multi-call binary.
> >
> > Usage: wget [-c|--continue] [--spider] [-q|--quiet] [-O|--output-document
> > FILE]
> > [--header 'header: value'] [-Y|--proxy on/off] [-P DIR]
> > [-S|--server-response] [-U|--user-agent AGENT] [-T SEC] URL.../
> >
> > Thus the external lib is not loaded.
> > Could you, please, help me to resolve the problem or provide me with
> another
> > way to add external libraries to Ignite classpath?
> >
> > Thanks in advance,
> > Ksenia
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: Docker deployment with EXTERNAL_LIBS environment variable

2018-04-17 Thread Roman Shtykh
I had the same problem (pretty common not having -i option) and fixed it. Need 
a review.https://issues.apache.org/jira/browse/IGNITE-8143
-- Roman
 

On Tuesday, April 17, 2018, 7:15:25 p.m. GMT+9, Petr Ivanov 
 wrote:  
 
 Hi, Kseniya.


I guess that something wrong with wget in distribution (alpine-linux). I will 
need some testing to investigate further.



> On 17 Apr 2018, at 13:02, Ksenia Vazhdaeva  wrote:
> 
> Hello,
> 
> I am trying to deploy Apache Ignite 2.4.0 in docker using external libs as
> described at https://apacheignite.readme.io/docs/docker-deployment
> 
> /docker run -d --name ignite -v
> /storage/ignite/ignite-server-config.xml:/etc/ignite/ignite-server-config.xml
> \
>    -e "CONFIG_URI=file:///etc/ignite/ignite-server-config.xml" -p
> 47500:47500 \
>    -e
> "EXTERNAL_LIBS=http://central.maven.org/maven2/org/apache/ignite/ignite-schedule/1.0.0/ignite-schedule-1.0.0.jar;
> \
>    apacheignite/ignite:2.4.0/
> 
> Docker container is started but in docker logs there is an error
> 
> /wget: unrecognized option: i
> BusyBox v1.27.2 (2017-12-12 10:41:50 GMT) multi-call binary.
> 
> Usage: wget [-c|--continue] [--spider] [-q|--quiet] [-O|--output-document
> FILE]
>     [--header 'header: value'] [-Y|--proxy on/off] [-P DIR]
>     [-S|--server-response] [-U|--user-agent AGENT] [-T SEC] URL.../
> 
> Thus the external lib is not loaded.
> Could you, please, help me to resolve the problem or provide me with another
> way to add external libraries to Ignite classpath?
> 
> Thanks in advance,
> Ksenia
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/