-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Packer docker builder does not reset ENTRYPOINT properly #7487
Comments
This is actually a issue with the Docker cli:
I suggest that you open an issue with Moby and link it here. |
The weird thing is if I pause packer (using debug mode) and run for example |
related: moby/moby#29502 |
I hit this issue too, and found a solution. This "builders": [
{
"type": "docker",
"image": "some_image",
"pull": true,
"commit": true,
"changes": [
"ENTRYPOINT [\"\"]",
"CMD [\"\"]"
]
}
], effectively reset the entrypoint to As I have never used it before, I'm not sure if this is a recent change in the way to specify it or a bug in the documentation, but 'works for me'. Hope this helps. |
One thing we could do is run |
Just ran into this. Using a base image with an Also, docs say that |
This issue has been automatically migrated to hashicorp/packer-plugin-docker#13 because it looks like an issue with that plugin. If you believe this is not an issue with the plugin, please reply to hashicorp/packer-plugin-docker#13. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
We are using packer to build a container with a parent that includes an entrypoint. In the packer build we "reset" entrypoint with
ENTRYPOINT []
. Unfortunately the container is being committed with the entrypoint of the parent still in place.Doing this in a Dockerfile gets rid of the entrypoint from parent:
While the same in packer version does not:
The text was updated successfully, but these errors were encountered: