Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Following The Instructions For Local Trains Deployment On Linux (

Following the instructions for local trains deployment on Linux ( https://allegro.ai/docs/deploying_trains/trains_server_linux_mac/ ) seems to download version 0.15.1-367 with a message suggesting an update

Even though the docker-compose.yml is actually downloaded from the master - this doesn't seem to be the intended behavior

  
  
Posted 3 years ago
Votes Newest

Answers 30


The instructions specify you should curl the latest docker-compose, which contains a reference to allegroai/trains:latest - currently, this image in docker hub is for Trains Server 0.16.1

  
  
Posted 3 years ago

Why would I have 0.15.1 if I followed the instructions of the docs?

  
  
Posted 3 years ago

Hi WackyRabbit7 ,
I'm not sure I follow - you have 0.15.1, and the UI suggests you upgrade to 0.161 - this is the expected behavior...

  
  
Posted 3 years ago

Did you install on a new machine or on a machine that previously had Trains Server installed?

  
  
Posted 3 years ago

Wait, suddenly the UI changed to 0.16.1, seems like I was shown a cached page

  
  
Posted 3 years ago

looks like it did pull the right image

  
  
Posted 3 years ago

Let me know if it doesn't work

  
  
Posted 3 years ago

SuccessfulKoala55 :shrug:

  
  
Posted 3 years ago

my bad, I didn't look at the upgrade section

  
  
Posted 3 years ago

I followed the upgrading still nothing

  
  
Posted 3 years ago

That's why we're here 😄

  
  
Posted 3 years ago

Still happens

  
  
Posted 3 years ago

Since the docker-compose.yml always points to the latest tag and not to a specific version tag (easier maintenance and uniformity), you have to pull if you're running in a machine that previously downloaded an image from this repo

  
  
Posted 3 years ago

Nope, standard docker behavior - it pulls only if it doesn't have any image for it or if you specified a non-existing tag...

  
  
Posted 3 years ago

mmmm got it

  
  
Posted 3 years ago

not manually I assume that if I deleted the image, and then docker-composed up, and I can see the pull working it should pull the correct one

  
  
Posted 3 years ago

I manually deleted the allegroai/trains:latest image, that didn't help either

  
  
Posted 3 years ago

Did you try to do docker pull ?

  
  
Posted 3 years ago

let me try to docker-compose down --rmi all

  
  
Posted 3 years ago

image

  
  
Posted 3 years ago

image

  
  
Posted 3 years ago

Don't assume 🙂 - just try to issue the command

  
  
Posted 3 years ago

This is why in the upgrade section we explicitly request you do:
docker-compose -f /opt/trains/docker-compose.yml pull

  
  
Posted 3 years ago

Yes, but docker already has the image cached...

  
  
Posted 3 years ago

When I said not the expected behavior, I meant that following the instructions on the docs, should lead to downloading the latest version

  
  
Posted 3 years ago

the curl refers to the master

  
  
Posted 3 years ago

but shouldn't the :lastest make it redownload the right image?

  
  
Posted 3 years ago

a machine that had previous installation, but I deleted the /opt/trains directory beforehand

  
  
Posted 3 years ago

The reference in the docker-compose.yml is for allegroai/trains:latest

  
  
Posted 3 years ago
549 Views
30 Answers
3 years ago
one month ago
Tags