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

install-utask.sh is not correctly updated #30

Closed
jorijinnall opened this issue Nov 21, 2019 · 1 comment · Fixed by #31
Closed

install-utask.sh is not correctly updated #30

jorijinnall opened this issue Nov 21, 2019 · 1 comment · Fixed by #31

Comments

@jorijinnall
Copy link

jorijinnall commented Nov 21, 2019

  • I'm submitting a ...

    • [ x] bug report
  • Do you want to request a feature or report a bug?
    Bug report
    install-utask.sh provided is not correctly updated when we download it :
    Steps to reproduce :

wget https://github.com/ovh/utask/releases/latest/download/install-utask.sh
docker-compose up
  • What is the current behavior?
docker-compose up
Starting utask_db_1    ... done
Starting utask_utask_1 ... done
Attaching to utask_utask_1, utask_db_1
utask_1  | time="2019-11-21T08:24:07Z" level=info msg="[DatabaseConfig] Using 50 max open connections, 30 max idle connections, 60 seconds timeout"
utask_1  | time="2019-11-21T08:24:08Z" level=fatal msg="dial tcp 172.18.0.3:5432: connect: connection refused"
db_1     | LOG:  database system was shut down at 2019-11-21 08:24:00 UTC
  • What is the expected behavior?
    Application is starting

  • Which version of uTask are you using?
    Latest version - 1.0.1 (see wget command)

  • Please tell us about your environment

lsb_release -d
Description:	Ubuntu 18.04.2 LTS
  • Other information
    This commit is not correctly applied to install-task.sh provided
    8ecc5dd

In docker-compose.yaml :

    depends_on:
      - db

is missing in utask section

After adding this part, application is starting correctly

--
I am not familiar on how install-script.sh is generated for the release, but if you have few guidelines, I will be glad to open a PR

@pablito-perez
Copy link
Contributor

Hi @jorijinnall , thanks for opening this issue. We became aware of this problem a few days ago and we've addressed it with PRs #23 and #27.
When we push the next tag on the repo you can expect a new install script to be released, pointing to a freshly built docker image which is able to wait for its db, as expressed in docker-compose.yaml (wait-for-it.sh)
I'll post an update on this issue when the new release is available
Regards,

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 a pull request may close this issue.

2 participants