You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two containers that I am experimenting using tini and su-exec with. The first container is a tomcat container and everything is working just fine, a text book example if you would.
The second container is a Redis container and this one for some reason only wants to run /bin/sh not what ever is in the CMD of the Dockerfile.
if [ "$1" = 'redis-server' -a "$(id -u)" = '0' ]; then
# Change the ownership
chown -R redis:redis /data
exec su-exec redis:redis "$@"
else
exec "$@"
fi
When I build and run this my container exits immediately.
docker logs -f redis is empty
docker inspect -f "{{.Name}} {{.Config.Cmd}}" $(docker ps -a -q)
/redis [/bin/sh]
/tomcat [start-app.sh catalina]
So I see that Tomcat is working but for some odd reason the Redis container is only running a shell.. The weird thing is both containers inherit from the same base Alpine container except the Tomcat container adds Java 8.
Any thoughts?
The text was updated successfully, but these errors were encountered:
Not sure if this is an issue or user error.
I have two containers that I am experimenting using tini and su-exec with. The first container is a tomcat container and everything is working just fine, a text book example if you would.
The second container is a Redis container and this one for some reason only wants to run /bin/sh not what ever is in the CMD of the Dockerfile.
The contents of start-app.sh are not much
When I build and run this my container exits immediately.
docker logs -f redis is empty
docker inspect -f "{{.Name}} {{.Config.Cmd}}" $(docker ps -a -q)
So I see that Tomcat is working but for some odd reason the Redis container is only running a shell.. The weird thing is both containers inherit from the same base Alpine container except the Tomcat container adds Java 8.
Any thoughts?
The text was updated successfully, but these errors were encountered: