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

fix: empty entrypoints in docker-compose=2.0.0.beta4 #464

Merged
merged 1 commit into from Jul 5, 2021

Conversation

regisb
Copy link
Contributor

@regisb regisb commented Jul 1, 2021

An issue with the latest release of docker-compose was reported here:
https://discuss.overhang.io/t/undefined-entrypoint-throws-error-in-docker-compose-2-0-0-beta-4/1716

The mysql-job definition had an empty entrypoint ([]). This was causing the following error:

the initiation of mysql fails with “services.mysql-job.entrypoint must be a string …
Error: Command failed with status 15”

I can't remember at all why we had to define an empty entrypoint. It probably
has to do with the fact that we could not run sh -e -c "..." commands in
mysql jobs. Similarly, the k8s job definition sets command: []. I tested both
local and k8s deployments without these definitions and they work just fine. So
I guess we can get rid of them.

@regisb regisb force-pushed the regisb/simplify-mysql-job-definition branch 2 times, most recently from a7d0627 to 055c5ac Compare July 1, 2021 05:19
@regisb
Copy link
Contributor Author

regisb commented Jul 1, 2021

This is ready for review @overhangio/tutor-developers.

Copy link
Member

@BbrSofiane BbrSofiane left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

An issue with the latest release of docker-compose was reported here:
https://discuss.overhang.io/t/undefined-entrypoint-throws-error-in-docker-compose-2-0-0-beta-4/1716

The mysql-job definition had an empty entrypoint (`[]`). This was causing the following error:

    the initiation of mysql fails with “services.mysql-job.entrypoint must be a string …
    Error: Command failed with status 15”

I can't remember at all why we had to define an empty entrypoint. It probably
has to do with the fact that we could not run `sh -e -c "..."` commands in
mysql jobs. Similarly, the k8s job definition sets `command: []`. I tested both
local and k8s deployments without these definitions and they work just fine. So
I guess we can get rid of them.
@regisb regisb force-pushed the regisb/simplify-mysql-job-definition branch from 055c5ac to 94bbb8d Compare July 5, 2021 07:57
@regisb regisb merged commit 6f04223 into master Jul 5, 2021
@regisb regisb deleted the regisb/simplify-mysql-job-definition branch July 5, 2021 08:01
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

Successfully merging this pull request may close these issues.

None yet

2 participants