revert directory-based mounting of entrypoint #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
if the directory the entrypoint is inside of is not mounted/created within the container image, then docker responds with an error about how the target directory does not exist. We can avoid this error by mounting the single file which docker recognizes as a "symlink"-style mount and can ignore the fact that its parent directories may not exist docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/home/tom/.local/bin/_denv_entrypoint": stat /home/tom/.local/bin/_denv_entrypoint: no such file or directory: unknown.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
if the parent of the directory of the entrypoint is not mounted/created
within the container image, then docker responds with an error about how
the target directory does not exist. We can avoid this error by mounting
the single file which docker recognizes as a "symlink"-style mount and
can ignore the fact that its parent directories may not exist