-
Notifications
You must be signed in to change notification settings - Fork 45
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
docker-compose.yml: stale 'frontend' network #830
Comments
3 tasks
oh sure, of course. I'll take a look today.
…On April 7, 2018 11:28:41 PM EDT, Ernesto Rodriguez Ortiz ***@***.***> wrote:
@kousu Could you review and test the PR #832?
Thanks in advance!
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#830 (comment)
--
kousu
|
Yes, of course, will do. Sorry, this got lost in my inbox.
7 avril 2018 23:28 "Ernesto Rodriguez Ortiz" a écrit:
@kousu (https://github.com/kousu) Could you review and test the PR #832 (#832)?
Thanks in advance!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (#830 (comment)), or mute the thread (https://github.com/notifications/unsubscribe-auth/AA8RX7q8GWMuUGWnSKmhyxsy2riP7ws4ks5tmYPpgaJpZM4Sb22O).
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you manually spawn into one of the docker containers you get this warning
This is because in
docker-compose.yml
Removing the
frontend:
line makes the warning go away.The text was updated successfully, but these errors were encountered: