epam / epam/Indigo

Indigo in a Docker container always has the previous version

Open
#909 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
406
Forks
134
Avg merge
2d 11h
Merged PRs (30d)
24

Description

Now I have installed version 1.8.2 from [this page](https://hub.docker.com/r/epmlsop/indigo-service/tags), and the code inside the container shows version `1.8.1.0-ge56b8acfc-x86_64-linux-gnu-11.2.1`.

Last time I used image `epmlsop/indigo-service:enhanced-1.8.1`, but Swagger saw version 1.8.0.

To be honest, I do not know if the version is displayed incorrectly or if you insert the previous version of Indigo into the container every time.

By the way, the [container with version 1.8.2](https://hub.docker.com/r/epmlsop/indigo-service/tags) was created 4 days ago, and this version was [released on GitHub](https://github.com/epam/Indigo/releases/tag/indigo-1.8.2) just an hour ago. It is possible that someone calls the container version incorrectly every time.

Contributor guide

No contributing guide indexed for this repository

Research direction

Inspect the epmlsop/indigo-service Docker tags and compare the Indigo version embedded in the 1.8.2 container with the GitHub indigo-1.8.2 release. Check the version reported through Swagger as well; the issue is done when the image tag, embedded version, and Swagger version consistently identify the same release.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.