[Docker]Force no-interaction mode on installation #702
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ferror
force-pushed
the
docker-old-minor
branch
from
ec0bace to
d57bc7e
Compare
coldic3
approved these changes
Apr 14, 2022
lchrusciel
approved these changes
Apr 14, 2022
|
@Ferror are you doing all these changes on the master branch? |
|
Thank you, Zbigniew! 🎉 |
Yup. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During an installation the composer asks for plugins (https://getcomposer.org/doc/06-config.md#allow-plugins) that leads to failing Docker build and making the terminal interactive.
How to reproduce the problem? Create a project from current Sylius-Standard and try to run
docker compose up -d