-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] critical error with max length project name #11818
Comments
Hello @aid219 |
yes, its compose project name. For example, here is a docker-compose.yml file, but only the length of the name was much longer_ name:"zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"
services:
golang:
build: ./
image: im21
container_name: golang21
restart: always
ports:
- 80:7667 |
Can you share the result of a |
yes, you're right, this is a docker desktop error, it stops from the terminal without any problems, do I need to send all the information to another branch again now, or can you somehow transfer it? |
Thanks, I would take care of it 👍 |
@aid219 what is your Docker Desktop version? Did you use WSL2 or Hyper-V as virtual machine? Are you using Windows or Linux containers? |
i use WSL2 |
and now I also cannot stop the container through the terminal as it turned out before, the command does not seem to do anything, as if it is executed without information output |
Hey @aid219 Can you reproduce this with a |
Without any feedback for several months, I'm closing the issue |
Description
I used the doker in conjunction with windows 10 and vs-code. I experimented with the "name:" parameter in docker-compose.yml" file, and when I entered a name there with a length of a couple thousand characters and launched - "docker-compose up -d " the image was created and the container started. But when I opened the desktop application after that, I could no longer stop the container or delete it, all my attempts were interrupted with an error of too long a name. Restarting the application and restarting the computer did not give results, as a result, I had to uninstall the docker application and install it again
Steps To Reproduce
No response
Compose Version
Docker Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: