How Do I Handle Entry Points in Docker Without Running Scripts in Bash?

Thanks for the clarification! It sounds like you're trying to mimic the behavior of other images where you don’t see the entrypoint running when you access bash. Many images use process managers like s6-overlay to handle this. This keeps the entrypoint running in the background while you interact with bash.

To keep it simple, you might consider setting up your own entrypoint script that manages how processes run. For instance, set up your entrypoint to run your checks and then execute the main command. Also, ensure your script's logic allows immediate feedback in the logs without having to engage with bash first.

A point that might help clarify things: when you open a bash shell, be sure you're not just creating a new container instance. Instead, you're looking at a fresh bash shell that doesn’t carry over the entrypoint processes that were started in the other container instance where you looked at the logs.

If you're not seeing scripts running in bash, it might be that you're starting a new environment. Make sure to check if you are running the commands in the same context!

If you want your validation output visible in the logs, ensure it writes to stdout or stderr. Sometimes, if you're missing log entries, it could be due to the logging format being json. Use tools like 'cat' or 'jq' to inspect logs directly. You can find where the logs are located using 'docker inspect'.

When you define both ENTRYPOINT and CMD in your Dockerfile, the CMD becomes the first argument given to the ENTRYPOINT. So, your container starts as "/entrypoint.sh /bin/bash". If you want to run an interactive container without triggering the entrypoint, use the --entrypoint argument in your 'docker run' command to override it. Here are some commands to consider:

- To run your container normally:
`docker run -ti myimage`
(this triggers the entrypoint)
- To drop into a bash shell without triggering the entrypoint:
`docker run -ti --entrypoint /bin/bash myimage`
- If you have a running container and want to access it:
`docker exec -ti /bin/bash`
This way, you can interact without executing your entrypoint script.