It is probably worth looking at this Galaxy issue - this may have
little to do with Docker or the Docker server might have a different
time configured than a local one? History updating is broken for many
clients in 16.04 and I am unsure if this intention is to fix it or
not.
https://github.com/ga
Hi George,
how do you start your container? Anything special in your network settings.
I can not reproduce this with 16.04 and 16.01 and have never seen this
before.
Which version of Docker? Is this under Linux?
I'm a little bit puzzled here.
Sorry,
Bjoern
> Hi Bjorn,
>
> We are using https:/
Hi,
this sounds strange :(
I will look at it asap. In the meantime can you please try this image:
https://quay.io/repository/bgruening/galaxy
Especially the 16.04 release. Dockerhub is completely unreliable for me
in the last month and quay.io works better for me.
Thanks for using Galaxy!
Bjoer
Hi George,
are you using this Docker container?
https://github.com/bgruening/docker-galaxy-stable
If so which version? I haven't seen this behaviour so far.
Ciao,
Bjoern
Am 14.04.2016 um 08:04 schrieb George Weingart:
> Hello,
>
> We are installing Galaxy in a Docker environment and we are en
Hello,
We are installing Galaxy in a Docker environment and we are encountering an
issue where we need to refresh the screen (For Example, using F5) in order
to see the status of the job.
We see that using chrome as browser.
If we don't refresh the screen, it stays (The job might have completed l