Skip to content
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

Help ERROR: The Compose file './docker-compose.yml' is invalid because #8

Open
vinhhathacha opened this issue Oct 17, 2024 · 4 comments

Comments

@vinhhathacha
Copy link

ERROR: The Compose file './docker-compose.yml' is invalid because:
services.execution-client.healthcheck value 'start_interval' does not match any of the regexes: '^x-'
services.op-node.healthcheck value 'start_interval' does not match any of the regexes: '^x-'
image

@voroningraphics
Copy link

try del '-' in docker-compose up -d
docker compose up -d

@Maxson71
Copy link

Maxson71 commented Nov 5, 2024

try del '-' in docker-compose up -d docker compose up -d

root@vmi2115775:~/unichain-node# docker-compose up -d
ERROR: The Compose file './docker-compose.yml' is invalid because:
services.execution-client.healthcheck value 'start_interval' does not match any of the regexes: '^x-'
services.op-node.healthcheck value 'start_interval' does not match any of the regexes: '^x-'
root@vmi2115775:~/unichain-node# docker compose up -d
[+] Running 3/3
 ✔ Network unichain-node_default               Created                                                                        0.1s 
 ✘ Container unichain-node-execution-client-1  Error                                                                          8.7s 
 ✔ Container unichain-node-op-node-1           Created                                                                        0.0s 
dependency failed to start: container unichain-node-execution-client-1 is unhealthy

image

@quyennguyentam43
Copy link

quyennguyentam43 commented Dec 9, 2024

I got the same issue, please help us fix it
image
log of unichain-node-execution-client-1 as bellow:

2024-12-09 23:50:10 exec /entrypoint.sh: no such file or directory

@quyennguyentam43
Copy link

This issue has resolved by by this way:

Cause and Solution for the exec /entrypoint.sh: no such file or directory Error
Cause:

This error usually occurs when the entrypoint.sh script has incorrect line endings. If the file was edited on Windows, it may have CRLF line endings instead of the Unix-compatible LF. Containers running on Linux cannot interpret CRLF, causing the file to be unreadable.
Solution:
Convert the file to Unix line endings (LF):
Use the following command to fix the line endings:

    dos2unix op-geth-entrypoint.sh

Alternatively, use a text editor (e.g., VS Code) to change the line endings:

  • Open the file.
  • In the bottom-right corner, click the line ending indicator (e.g., CRLF).
  • Select LF (Unix) and save the file.

Ensure the script is executable:
Make the script executable with:
chmod +x op-geth-entrypoint.sh

Recreate the containers to apply the changes:

    docker-compose down
    docker-compose up

With these steps, the container should now recognize and execute the entrypoint.sh script correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants