-
Notifications
You must be signed in to change notification settings - Fork 74
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
podman entrypoint for working container #258
Comments
Hello! I can see three options here:
Not sure if this is a change podman did recently because I don't recall this behaviour wrt entrypoint. I could have some bandwidth this week to implement 3) though can't promise it. |
Yea I'll go through with 1 for now; I dug through the code for running commands but I'm not confident in creating a useful PR with my schedule at the moment. I may try to jump in next week when I have more time if you haven't gotten to it by then. No worries on timing man, appreciate the work you've done so far. I was mostly checking to see if I was missing something that I didn't understand. |
Sadly my extra time got absorbed by the sickness from the second covid dose :/ it would take me weeks to get to this because of my current plans. Let me know if you need any further help and I'll try to assist as soon as I find time. Obviously, long term, we should do 3) and actually fix this in bender, so I'm glad we have a solid workaround in the meantime. |
Hi, I've been doing some testing with bender to replace our AMIs with Docker containers.
One of the things I'm trying to accomplish is setting up our Ubuntu-based Jenkins agents in Docker through ECS+Fargate.
My pipeline is:
base -> jenkins-base
jenkins-base -> infrastructure
jenkins-base -> java
jenkins-base -> etc.
During my jenkins-base creation, I set the target_image entrypoint to /usr/local/bin/jenkins-agent - which is required behavior for ECS as it passes a command expecting it to be an argument to that shell script.
Unfortunately, this means in my infrastructure/java/etc. images- the ansible-bender build fails, "can't find python".
The only way I can figure out how to get around this is to not set the entrypoint in my jenkins-base and set it in the downstream containers- which isn't ideal.
Am I missing another way?
Logs here:
The text was updated successfully, but these errors were encountered: