Docker interactive shell keeps running anytime I run docker commands

I’m working with developing a chatbot, and I’m trying to re-build my docker image and container after I edited some updates to my code. I had to force quit on my old docker image since it was struggling to load, and now it won’t open for good. Despite this, I still have a docker extension and running the command, ‘docker --version’ gives me the version I’m using.

The problem is, every time I run a command like ‘docker build -t .’ for my image, the shell I’m using for my vscode terminal automatically launches a docker interactive shell. I could run ‘docker ps’ or ‘docker images’ and would get the same result.

I initially thought it was an alias or configuration issue, but after running some commands, it seems like there were no conflicting alias shells.

I also checked my dockerfile code and it seems like there should be no misconfigurations. I also tried checking if my code has any instruction that requires user input, but this also seems to yield no such case.

At this point, I’m unsure if there’s an override within my commands or a build log which may have caused the interactive shell to activate based on a certain prompt.

Hi Anastasia, thank you for the reply. I forgot to edit the post but I actually solved the issue a while ago. It turned out I had to force quit on my applications, and I believe my docker app was still running.

Essentially, I had to delete it and re-install docker and ran some commands. At that point, it had worked out.

Thank you once again, this occurred a couple months ago and I was able to fix the issue a couple of weeks later.

Thank you for sharing your solution. Just for others who don’t understand what you replied to:

It was a (possibly AI-generated) spam post, which I deleted.

This topic was automatically closed after 4 days. New replies are no longer allowed.