question-mark

Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Can't start containers after 2.6.2 update - reports wrong Compose file version

See original GitHub issue

Issue Description

Describe the bug

  • Tested on Linux Mint 19.3
  • Clean install of 2.6.2, using node/npm 12.13.1 installed via nvm.
  • Try to run any command in 10updocker:

ERROR: Version in “./docker-compose.yml” is unsupported. You might be seeing this error because you’re using the wrong Compose file version. Either specify a supported version (e.g “2.2” or “3.3”) and place your service definitions under the services key, or omit the version key and place your service definitions at the root of the file to use version 1.

  • No containers are created, the process halts.
  • If instead of running 10updocker start I run docker-composer up all containers are started without errors, but the database is unreachable.
  • Changing the version in the project’s docker-compose.yml does nothing.

Complete output below, trying to start an existing project

$ 10updocker start
WARNING: No swap limit support
Locating project files for projectname-local
Ensuring global network exists
 - Network exists
Ensuring global cache volume exists
 - Creating Volume
Ensuring global services are running
ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version (e.g "2.2" or "3.3") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/
(node:5738) UnhandledPromiseRejectionWarning: Error: Command failed: docker-compose up -d
    at checkExecSyncError (child_process.js:621:11)
    at execSync (child_process.js:657:15)
    at startGateway (/home/ricardo/.nvm/versions/node/v12.13.1/lib/node_modules/wp-local-docker/src/gateway.js:114:5)
    at Object.startGlobal (/home/ricardo/.nvm/versions/node/v12.13.1/lib/node_modules/wp-local-docker/src/gateway.js:138:11)
    at async start (/home/ricardo/.nvm/versions/node/v12.13.1/lib/node_modules/wp-local-docker/src/environment.js:52:5)
(node:5738) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:5738) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Steps to Reproduce

  1. Go to ‘…’
  2. Click on ‘…’
  3. Scroll down to ‘…’
  4. See error

Expected behavior

Commands run and containers are initialized without errors

Screenshots

Environment information

  • Device: Dell XPS
  • OS: Linux Mint 19.3

Additional context

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:6

github_iconTop GitHub Comments

1reaction
moraleidacommented, Jan 6, 2020

@tylercherpak yes, upgrading docker-compose solved it. We can close this out. Thanks!

0reactions
eugene-manuilovcommented, Jan 26, 2021

Closing this ticket.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Compose file versions and upgrading - Docker Documentation
This table shows which Compose file versions support specific Docker releases. ... As a result, features added in later versions will not be...
Read more >
24 - Stack Overflow
Your compose is too old, if you cannot change the version in compose, try to upgrade to latest docker-compose version
Read more >
Docker Compose release notes
docker-compose ps now shows the containers' health status if available ... Note: This feature will not be ported to version 3 Compose files....
Read more >
Updating the project - IOTstack
Troubleshooting: if a container fails to start after update¶ · check that you have a backup. · stop and remove Docker containers: docker-compose...
Read more >
How To Install and Use Docker Compose on Ubuntu 22.04
Docker Compose is a tool that allows you to run multi-container ... The docker-compose.yml file typically starts off with the version ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found