Thank you very much!! I'm looking for that long time ago!
@joanmedia Жыл бұрын
So happy to hear that. Hope you find it usefull :)
@QAStefanini Жыл бұрын
Awesome!
@actionimme Жыл бұрын
The dot in docker build specifies the build context. The dockerfile location only defaults to the same dir. Can be set with the -f flag as well. It's not the same thing
@joanmedia Жыл бұрын
Received the same feedback from another folk 😅 thanks for the feedback 🫡🙌🏼
@RealEstate3D Жыл бұрын
In „docker run“ -t equals -tty. It doesn’t set the image tag…In contrast to the „docker build“ where -t sets the image:tag.
@joanmedia Жыл бұрын
Hello Real Estate, you are totally right. Thanks for the comment/feedback :) So happy to see my mistake. Detailed explanation: The -t (or --tty) flag tells Docker to allocate a virtual terminal session within the container. This is commonly used with the -i (or --interactive) option, which keeps STDIN open even if running in detached mode (more about that later
@RealEstate3D Жыл бұрын
@@joanmedia And if it’s a running one “docker attach ”. But leaving this session without killing the process ... is kind of leaving vim :)
@ЕвгенийБелецкий-к5в Жыл бұрын
Hi Joan! Thanks for video! I have a question: all works well, as you show. But after I changed my scenario and add new feature file in folder, but terminal says that have not found file. So any changes won't work. It means i nedd after any changes create new image and run container? sounds not good. It is possible to run container with installed dependencies but with me feature files that I edited or add at my local machine? Thanks!
@user-hm9ee5oh8l Жыл бұрын
I am getting this error: we looked for but did not file cypress json file in folder /e2e. can you please help with this?