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.

Sign up for GitHub

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

Jump to bottom

Latest chart version image with problem #83

Closed
JulianPedro opened this issue Jan 10, 2023 · 3 comments · Fixed by #86
Closed

Latest chart version image with problem #83

JulianPedro opened this issue Jan 10, 2023 · 3 comments · Fixed by #86
Assignees
@sheldonhull
Labels
bug Something isn't working

Comments

@JulianPedro
Copy link

Environment

  • Minikube v1.25.2 on Arch 22.0.0 (Tested with Docker and Virtualbox Driver)

Problem

image

After updating the image repository to docker, installing chart has this problem. The version with the old repository (quay.io) works fine.

I think the image is the problem.

Other related issue

image

We also use another way of using Delinea, related to kuberentes (Sidecar), the image was updated some time ago and changed from amd64 to arm64, can you fix that?

Before this update the latest version was amd64 and worked relatively well.
@sheldonhull sheldonhull self-assigned this Jan 23, 2023
@sheldonhull sheldonhull added the bug Something isn't working label Jan 23, 2023
@sheldonhull
Copy link
Contributor

sheldonhull commented Jan 23, 2023 •
edited
Loading

First off, I'm sorry there was a delay in responding to you. I didn't see any notification of this new issue being reported! Most of the requests for support come through our support team. I'll see if I can improve this so you get a response in the future much sooner.

I think you might have gotten help on this but can you confirm by closing as resolved or update here if you still need help? The dsv-k8s-controller project is a different one from this, but. think you'll find the latest amd64 build is on latest tag now in dockerhub.

We'll migrate that image eventually over to the new DelineaXPM org in docker org in docker too, but haven't had a chance to do that yet.

EDIT: Rereading this I think you are reporting both this project + the related "dsv-k8s-controller" issue as seperate issues, and so you are still running into the dsv-k8s injector/syncer image failing, correct?

@sheldonhull
Copy link
Contributor

sheldonhull commented Jan 24, 2023 •
edited by azure-boards bot
Loading

related AB#483421 - I've identified a fix for the image not finding the injector/syncer and should have out shortly.

@sheldonhull sheldonhull mentioned this issue Jan 25, 2023
Merged
sheldonhull added a commit that referenced this issue Jan 25, 2023
@sheldonhull
fix: resolve incorrect binary path for docker hub based images (#86)
707a3d5 
- Fixes #83 reported by @JulianPedro 👍
- Development tooling tweaks to work on addressing some timeouts in
devcontainers.
This isn't confirmed resolved as not sure if vscode configuration issue,
codespaces issue, or something else causing this.
Local development works fine, but container based workspaces seem to
have timeouts randomly.
- Create a new dockerhub release.  
- fixes
[AB#483421](https://thycotic.visualstudio.com/4a89362e-1361-424f-a291-a8f57c2a8991/_workitems/edit/483421)
#83
@sheldonhull
Copy link
Contributor

Published updated image. Closing as resolved, reopen if you see anything else not working for you now @JulianPedro. cheers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sheldonhull sheldonhull

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: resolve incorrect binary path for docker hub based images DelineaXPM/dsv-k8s
2 participants
@sheldonhull @JulianPedro