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

fix(docker/kumactl): add entrypoint to kumactl img #6593

Merged

Conversation

bartsmykla
Copy link
Contributor

@bartsmykla bartsmykla commented Apr 24, 2023

Without specifying entrypoint inside the Dockerfile, it was impossible to use the image without having to do it explicitly during the container start

It was impossible to do:

docker run kumahq/kumactl:2.2.0 kumactl version
# /busybox/sh: can't open 'kumactl': No such file or directory

and you had to explicitly specify entrypoint

docker run --entrypoint /usr/bin/kumactl kumahq/kumactl:2.2.0 version
# Client: Kuma 2.2.0
# Unable to connect to control plane: Get "http://localhost:5681/": dial tcp 127.0.0.1:5681: connect: connection refused

before:

docker run kumahq/kumactl:2.0.0 kumactl version
# Client: Kuma 2.0.0
# Unable to connect to control plane: Get "http://localhost:5681/": dial tcp 127.0.0.1:5681: connect: connection refused

Closes: #6566

Checklist prior to review

Without specifying entrypoint inside the Dockerfile, it was
impossible to use the image without having to do it explicitly
during the container start

It was impossible to do:
```sh
docker run kumahq/kuma:2.2.0 kumactl version
```
and you had to explicitly specify entrypoint
```sh
docker run --entrypoint /usr/bin/kumactl kumahq/kuma:2.2.0 version
```

Signed-off-by: Bart Smykla <bartek@smykla.com>
@bartsmykla bartsmykla requested review from a team, slonka and lukidzi and removed request for a team April 24, 2023 07:01
@bartsmykla
Copy link
Contributor Author

@Mergifyio backport release-2.2 release-2.1

@mergify
Copy link
Contributor

mergify bot commented Apr 24, 2023

backport release-2.2 release-2.1

✅ Backports have been created

@bartsmykla bartsmykla enabled auto-merge (squash) April 24, 2023 07:12
@michaelbeaumont
Copy link
Contributor

Also I think this is more fix(kumactl)/fix(docker). We use the image in Helm charts + it's published.

@bartsmykla bartsmykla changed the title ci(docker/kumactl): add entrypoint to kumactl img fix(docker/kumactl): add entrypoint to kumactl img Apr 24, 2023
@bartsmykla
Copy link
Contributor Author

bartsmykla commented Apr 24, 2023

Also I think this is more fix(kumactl)/fix(docker). We use the image in Helm charts + it's published.

Agree. Adjusted the PR's name.

@bartsmykla bartsmykla merged commit fe153f0 into kumahq:master Apr 24, 2023
@bartsmykla bartsmykla deleted the ci/add-entrypoint-for-kumactl-image branch April 24, 2023 07:45
mergify bot pushed a commit that referenced this pull request Apr 24, 2023
Without specifying entrypoint inside the Dockerfile, it was
impossible to use the image without having to do it explicitly
during the container start

It was impossible to do:
```sh
docker run kumahq/kuma:2.2.0 kumactl version
```
and you had to explicitly specify entrypoint
```sh
docker run --entrypoint /usr/bin/kumactl kumahq/kuma:2.2.0 version
```

Signed-off-by: Bart Smykla <bartek@smykla.com>
(cherry picked from commit fe153f0)
mergify bot pushed a commit that referenced this pull request Apr 24, 2023
Without specifying entrypoint inside the Dockerfile, it was
impossible to use the image without having to do it explicitly
during the container start

It was impossible to do:
```sh
docker run kumahq/kuma:2.2.0 kumactl version
```
and you had to explicitly specify entrypoint
```sh
docker run --entrypoint /usr/bin/kumactl kumahq/kuma:2.2.0 version
```

Signed-off-by: Bart Smykla <bartek@smykla.com>
(cherry picked from commit fe153f0)
mergify bot added a commit that referenced this pull request Apr 24, 2023
…6594)

ci(docker/kumactl): add entrypoint to kumactl img (#6593)

Without specifying entrypoint inside the Dockerfile, it was
impossible to use the image without having to do it explicitly
during the container start

It was impossible to do:
```sh
docker run kumahq/kuma:2.2.0 kumactl version
```
and you had to explicitly specify entrypoint
```sh
docker run --entrypoint /usr/bin/kumactl kumahq/kuma:2.2.0 version
```

Signed-off-by: Bart Smykla <bartek@smykla.com>
(cherry picked from commit fe153f0)

Co-authored-by: Bart Smykla <bartek@smykla.com>
mergify bot added a commit that referenced this pull request Apr 24, 2023
…6595)

ci(docker/kumactl): add entrypoint to kumactl img (#6593)

Without specifying entrypoint inside the Dockerfile, it was
impossible to use the image without having to do it explicitly
during the container start

It was impossible to do:
```sh
docker run kumahq/kuma:2.2.0 kumactl version
```
and you had to explicitly specify entrypoint
```sh
docker run --entrypoint /usr/bin/kumactl kumahq/kuma:2.2.0 version
```

Signed-off-by: Bart Smykla <bartek@smykla.com>
(cherry picked from commit fe153f0)

Co-authored-by: Bart Smykla <bartek@smykla.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

docker run kumahq/kumactl:2.1.0 kumactl returns /busybox/sh: can't open 'kumactl'
3 participants