I am trying to run a container and modify certain files in it. I am trying to do this using a script. If I use:
docker run -i -t <container> <image>, it is giving me
STDERR: cannot enable tty mode on non tty input
If I use:
docker run -d <container> <image> bash, the container is not starting.
Is there anyway to do this?
Thanks
Run the docker image in background using:
docker run -d <image>:<version>
Check running docker containers using:
docker ps
If there is only one container running you can use below command to attach to a running docker container and use bash to browser files/directories inside container:
docker exec -it $(docker ps -q) bash
You can then modify/edit any file you want and restart the container.
To stop a running container:
docker stop $(docker ps -q)
To run a stopped container:
docker start -ia $(docker ps -lq)
docker commit the doc docs.docker.com/reference/commandline/cli/#commit
STDERR: cannot enable tty mode on non tty input error. I think the bestway is share volumes between container and host. But when I'm sharing a directory between host and container, the files in the container folder are getting replaced by the files in the host. If the host directory is empty then all my files in the container are lost. Is there any way to share container files into host. thanks
docker exec from inside shell scripts. Show your script by editing your question so that I can investigate it.docker run --name container-name -v /home/my_files/:/home/container/files -d <image> this command is doing nothing. Moreover if I need to edit certain configuration files before I start my tomcat in container, what is the best way to do this.docker run starting your container?So to start off, the -i -t is for an interactive tty mode for interacting with the container. If you are invoking this in a script then it's likely that this won't work as you expect.
This is not really the way containers are meant to be used. If it is a permanent change, you should be rebuilding the image and using that for the container.
However, if you want to make changes to files that are reflected in the container, you could consider using volumes to mount directories from the host into the container. This would look something like:
docker run -v /some/host/dir:/some/container/dir -d container
At this point anything you change within /some/host/dir will be within the container at /some/container/dir. You can then make your changes with a script on the host, without having to invoke the docker cli.
docker eventsshows when you container fails?