-
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] <title>Error: 'docker-compose up -d' Fails with KeyError: 'ContainerConfig #11742
Comments
I have just encountered the same problem on Debian 11, following a docker update from 24 to 26. $ sudo apt list --upgradable | grep docker
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
docker-buildx-plugin/bullseye 0.13.1-1~debian.11~bullseye amd64 [pouvant être mis à jour depuis : 0.11.2-1~debian.11~bullseye]
docker-ce-cli/bullseye 5:26.0.1-1~debian.11~bullseye amd64 [pouvant être mis à jour depuis : 5:24.0.7-1~debian.11~bullseye]
docker-ce-rootless-extras/bullseye 5:26.0.1-1~debian.11~bullseye amd64 [pouvant être mis à jour depuis : 5:24.0.7-1~debian.11~bullseye]
docker-ce/bullseye 5:26.0.1-1~debian.11~bullseye amd64 [pouvant être mis à jour depuis : 5:24.0.7-1~debian.11~bullseye]
docker-compose-plugin/bullseye 2.26.1-1~debian.11~bullseye amd64 [pouvant être mis à jour depuis : 2.21.0-1~debian.11~bullseye] I haven't read the entire changelog, but it's time to upgrade to docker compose v2 to fix this. On my side, to fix the problem, I replaced the commands |
You're using docker-compose version 1.29.2, which is End of Life for 1 year now. I'm closing this issue as "won't fix" |
So docker is aimed support to allows decade-old apps to keep them running in a container, but can't maintain a stability with its own Python library from a couple of years ago? Why was compatibility broken with the Python library in the first place, do you have a reference issue about this? |
Docker compose v1 (python) has been deprecated 2 years ago and announced end of life 1 year ago (see https://github.com/docker/compose/tree/v1)
I can't tell what's broken with your installation, haven't investigated as we don't support this codebase anymore. |
Description
Hello
Since some time, I am no longer able to use the command "docker-compose up -d" after performing a docker-compose pull, for example.
For your information, my configuration has been working perfectly for almost two years, and I haven't made any particular modifications other than my weekly system updates.
Here's the error message I'm encountering:
Do you have any ideas or knowledge about this issue?
Thank you
Have a great day
Steps To Reproduce
docker-compose pull
docker-compose up -d
Compose Version
Docker Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: