Hi;
The problem is definitively Galaxy related, and the cause seems to be that
my program, when invoked in the Docker image from Galaxy, it's unable to
resolve the service host. The weird thing is that it can resolve it when
invoked within Docker, so there must be a problem with how Galaxy invokes
Hi again;
I can execute Docker tools from Galaxy (thanks!), however now I have a
further problem that must be Galaxy-related and I can't debug straight
away. My Galaxy tool is a simple java jar that gets a service URL and an
RDF file as inputs [1], invokes the service by POSTing the RDF to the URL
2015-08-19 15:50 GMT+02:00 John Chilton :
> I don't know to be honest - a couple of things to verify.
>
> I wrote a bunch of debug stuff right away at the end of the e-mail and
> you can try if I am wrong, but after I wrote I realized the problem.
> You are not using sudo for running docker in you
I don't know to be honest - a couple of things to verify.
I wrote a bunch of debug stuff right away at the end of the e-mail and
you can try if I am wrong, but after I wrote I realized the problem.
You are not using sudo for running docker in your examples - this is
paused because sudo is waiting
Hi;
I'm trying to develop a Docker based tool, as suggested by a peer-reviewer
who might be reading this :P
However, I'm having trouble with even the most basic setting, and I don't
know what might be wrong, so any help will be much appreciated. I have
developed a very simple docker image and cor