Are there stable-release container tags on docker hub?

62 views
Skip to first unread message

Michael Kirk

unread,
Jan 4, 2023, 1:10:34 PM1/4/23
to OpenTripPlanner Users
Is there a docker tag for the latest stable containers on docker hub?

Since v2.2.0, the project has been pushing OCI containers to dockerhub. I believe this is done automatically per commit via CI.

You can see all the container tags here: https://hub.docker.com/r/opentripplanner/opentripplanner/tags

Looking at those tags, it looks like there's a tag for every commit. For stability, I want to run a container corresponding to the 2.2.0 release, not some interstitial "unreleased" build.


Am I missing something — do these tags exist somewhere? If not, would the project maintainers consider pushing a "stable" docker tag for every versioned release?

Thanks!

Leonard Ehrenfried

unread,
Jan 4, 2023, 3:24:14 PM1/4/23
to OTP Users
The release version tags don't exist because when I set up the CI pipeline there wasn't a easy way to do so and I myself only ever use the latest dev version.

I had vague intentions of adding the release tags but never actually got round to doing it.

Now that I know that someone else is using these images, I can add them. Hopefully I will get to it next week. If I forget you can prod me.

Btw, the corresponding tag to the 2.2 release would be 0e15511b630347df581f1f230de7f470db1b7b26

Best.

--
  Leonard Ehrenfried
--
You received this message because you are subscribed to the Google Groups "OpenTripPlanner Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opentripplanner-...@googlegroups.com.

Leonard Ehrenfried

unread,
Jan 9, 2023, 4:41:51 AM1/9/23
to OTP Users

Michael Kirk

unread,
Jan 19, 2023, 2:00:32 PM1/19/23
to Leonard Ehrenfried, OTP Users
I finally made some time to leverage the docker container in my workflow.

Unfortunately I encountered an [^error] when starting the server with the 2.2.0 tag, so I ended up using a more recent nightly build anyway. :shrug:

In the future, I do intend to use tagged point releases, under the presumption that _generally_ tagged releases are a more stable target.

Thank you for doing this!

---

[error]

With the 2.2.0 tagged release, I was able to --build, but during server `--load` I saw:

```
     headway-opentripplanner-1            | 01:41:14.080 ERROR (OTPMain.java:58) An uncaught error occurred inside OTP: Cannot invoke "java.util.Set.iterator()" because "patterns" is null
     headway-opentripplanner-1            | java.lang.NullPointerException: Cannot invoke "java.util.Set.iterator()" because "patterns" is null
```

I didn’t encounter this error when building/serving with: opentripplanner/opentripplanner:2.3.0_2023-01-17T14-05@sha256:794c9ef30ba6e49d91eebd0ae5673c3cbbaa40b8ed806243f9f666a3d8dc5afb


You received this message because you are subscribed to a topic in the Google Groups "OpenTripPlanner Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/opentripplanner-users/4suK0JaVMoY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to opentripplanner-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/opentripplanner-users/8cc70d53-4f7c-42c8-bf5c-3513eac82310%40app.fastmail.com.

Reply all
Reply to author
Forward
0 new messages