NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #1933 by repository stars
Latest stable
v1.4.5
Last release 9 years ago
no release in 18 months
Release timing varies
gaps range from 9 days to 6 months
Some releases are documented
notes for 14 of 26 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
28 releases · first in 2015
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Fixes issue with duplicate Websocket endpoints
Fixes issue with duplicate Websocket endpoints
Latest release available on the Docker Store: ehazlett/interlock:1.4.3
Fixed issue with SSL and custom ports
Fixed issue with SSL and custom ports (https://github.com/ehazlett/interlock/pull/238)
Latest release available on the Docker Store: ehazlett/interlock:1.4.2
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Fixes bug where a container with a private port only and no interlock.port label would use a 0 port
Patch release v1.4.1
interlock.port label would use a 0 port (https://github.com/ehazlett/interlock/issues/237)Latest release available on the Docker Store: ehazlett/interlock:1.4.1
Performance improvements to reduce Docker API load and improve stability
This is a performance update.
The latest image is available on the Docker Store: ehazlett/interlock:1.4.0
This is the latest release in the 1.3.x series. The following fixes and enhancements are included:
This is the latest release in the 1.3.x series. The following fixes and enhancements are included:
The latest image is available on the Docker Store: ehazlett/interlock:1.3.2
Nothing published for this version
Nothing published for this version
This release contains a few bug fixes:
This release contains a few bug fixes:
Docker Image is available at ehazlett/interlock:1.3.0 (https://hub.docker.com/r/ehazlett/interlock/) as well as ehazlett/interlock:latest.
This is the milestone release for 1.2. It contains several fixes and includes new polling support.
This is the milestone release for 1.2. It contains several fixes and includes new polling support.
Docker Image is available at ehazlett/interlock:1.2.0 (https://hub.docker.com/r/ehazlett/interlock/)
Note: the latest tag on the Docker Hub has been updated this release to point to 1.2.0. If you need to use the legacy release (not recommended) you can access it via ehazlett/interlock:legacy.
Bug fixed: if Interlock was launched on a Swarm manager that did not have a Swarm agent, restart events were missed
This is a bug fix release.
Docker Image is available at ehazlett/interlock:1.1.3 (https://hub.docker.com/r/ehazlett/interlock/)
fixed bug where configuration was being forced and environment was being ignored
This is a minor update.
Docker Image is available at ehazlett/interlock:1.1.2 (https://hub.docker.com/r/ehazlett/interlock/)
Add ability to enable/disable rewrites for context roots
Many thanks to the following contributors this release!:
Docker Image is available at ehazlett/interlock:1.1.1 (https://hub.docker.com/r/ehazlett/interlock/)
fix SSL / SNI verification bug (thx @owen!)
INTERLOCK_CONFIG containing the configuration as text)Docker Image published as ehazlett/interlock:1.1.0
NOTE: this is a major refactor from the previous version of Interlock. See the "Major Changes" below for details.
Interlock 1.0!
NOTE: this is a major refactor from the previous version of Interlock. See the "Major Changes" below for details.
The "latest" Docker Image tag will remain pointed at v0.3.3, the legacy version. This is to allow for current users to migrate. The "latest" Docker Image tag will be updated as the new version after a couple of releases to allow for migration from legacy users. It is strongly recommended to use the latest release as legacy is no longer maintained.
See https://hub.docker.com/r/ehazlett/interlock/ for the Docker Images
Nothing published for this version
Fixed backwards compatibility bug with Nginx plugin. If using the pre-0.3.0 ports (8080/8443) the upstreams would not be configured properly.
SSL Backend support, bug fixes.
SSL Backend support, bug fixes.
Note: this changes the default HAProxy ports to listen on 80 and 443.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.