Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker container behaves not as expected. #427

Closed
VolkerHartmann opened this issue Dec 12, 2023 · 1 comment
Closed

Docker container behaves not as expected. #427

VolkerHartmann opened this issue Dec 12, 2023 · 1 comment
Labels
docker good first issue Good for newcomers

Comments

@VolkerHartmann
Copy link
Contributor

Describe the bug
I use the 'latest' version of the docker image.
After starting container referring to the 'latest' version not
everything works like documented.

To Reproduce
Steps to reproduce the behavior:

  1. Start docker container: 'docker run -d -p8040:8040 --name metastore4docker kitdm/metastore2:latest'
  2. Try to get info about service 'curl 'http://localhost:8040/metastore/actuator/info' |jq
    {
    "timestamp": "2023-12-12T06:56:15.901+0000",
    "status": 404,
    "error": "Not Found",
    "message": "No message available",
    "path": "/metastore/actuator/info"
    }
    ....'

Expected behavior
The current version should be printed.

@VolkerHartmann VolkerHartmann pinned this issue Dec 12, 2023
@VolkerHartmann
Copy link
Contributor Author

Unfortunately, Docker will not update the local container if the tag used is already available.
I recommend always using the version tag.
For example: docker run -d -p8040:8040 --name metastore4docker kitdm/metastore2:v1.3.0

If you want to use the 'latest' version (which should always be identical to the last version), please do the following

docker pull kitdm/metastore2:latest

You may need to remove existing images first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docker good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant