Respond to Prompt in Bash Script
I work on a project that requires I frequently build and destroy a virtual machine. I don't enjoy having to do so but virtual machines can be notoriously difficult to prop up, especially when you have a complex app living within it.
Manually typing the same commands over and over can be mind-numbing so I've create a bash script to handle all of the work for me. One hiccup to the process is needing to confirm removal of an existing virtual machine; using a pipe and echo allows me to answer the prompt:
# ... some directives here
# Remove the machine, confirming "y" when asked by docker-machine
echo 'y' | docker-machine rm default
# ... more directives here
Using echo I pipe a y response to docker-machine's confirmation prompt, thus allowing the script to move forward with other tasks without the need for manual intervention.
I don't, however, know how to handle multiple prompts -- can you tell me and everyone else?
![I’m an Impostor]()
This is the hardest thing I've ever had to write, much less admit to myself. I've written resignation letters from jobs I've loved, I've ended relationships, I've failed at a host of tasks, and let myself down in my life. All of those feelings were very...
![Page Visibility API]()
One event that's always been lacking within the document is a signal for when the user is looking at a given tab, or another tab. When does the user switch off our site to look at something else? When do they come back?
![Making the Firefox Logo from HTML]()
When each new t-shirt means staving off laundry for yet another day, swag quickly becomes the most coveted perk at any tech company. Mozilla WebDev had pretty much everything going for it: brilliant people, interesting problems, awesome office. Everything except a t-shirt.
That had to change.
The basic...
![Introducing MooTools NextPrev]()
One thing I love doing is duplicating OS functionalities. One of the things your OS allows you to do easily is move from one item to another. Most of the time you're simply trying to get to the next or the previous item.
As far as I know this is usually done with the yes command:
This should also respond to multiple prompts.
Ah yes, I did experiment with that. But what if I know the multiple prompt responses should be “y”, “n”, “3”? That would be useful.
To expand on what Andreas said, you can build a canned file of responses, one per line (extra blanks for the equivalent of hitting enter) and sending that to your program:
Can’t you stream a file in? Like in
Try a here string.
while IFS= read -r; do echo "E- $REPLY" done <<<"y n 3"Will print the three lines of responses. Assuming the docker prompt is similar to read it should work.
The ‘expect’ utility can be installed on most Linux boxes.
https://en.wikipedia.org/wiki/Expect
I agree about ‘expect’ as Rohit mentions, it’s usually what you resort to when piping doesn’t work for different reasons (such as passwords being read from physical terminal only, input being prematurely consumed by a loop, etc).
The tool is {advanced|complicated} enough to maybe warrant a future post ;-)
In my team we use Vagrant and Ansible to do these kinds of things. They are very helpful tool for popping up a dev env with customized apps / configs.
I have not tried Ansible for Docker but there is a page for it https://www.ansible.com/docker