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

EZP-27788: Update and cleanup docker config for Docker 17.06 features #192

Merged
merged 10 commits into from
Aug 24, 2017

Conversation

andrerom
Copy link
Contributor

@andrerom andrerom commented Jul 12, 2017

Issue: https://jira.ez.no/browse/EZP-27788
Epic: https://jira.ez.no/browse/EZP-26310

Docker 17.06 came out in June, and with it these notable features are now in stable channel which we haven't started using yet:

Todo / TBD

  • Currently blocked on bug in Docker 17.06 that is solved in 17.06.01-rc false poitive during testing, the issue was something else 😕
  • Update doc to refer to launchpad for simple use cases_commited to active branches ahead of 1.11 release in 7f2abb5acd555a0c70a8a5c77c04814be2e3af41_
  • Rename doc/docker-compose to doc/docker and adapt yml/doc given it is about more then just docker-compose now ( and shorter paths ;) )
  • Test on kernel repo to make sure this does not break sub repo testing: Passing

Possible followups:

Now that Docker 17.06 stable release is out, `:cached` and other features
are now available in stable versions and can be used (17.04/5: edge).

Bumps compose version all the way up to 3.3 which came in 17.06 for
future use and hopefully not having to bump in in a while.
Should theoretically get rid of the issue where app image starts up
before mariadb is ready for connections, leading to user reaching 500 page.

Note: The previous commit adding cached mounts for the sql file mostly fixes the
      issue, but this commit should in theory avoid app contianer starting to early.
…ust compose files

As a bonus this also shorten the paths when working with the files.
… are for

Aslo rather add links to Launchpad for people wanting to get up and running easily.
@andrerom andrerom requested a review from vidarl August 21, 2017 11:50
@andrerom andrerom changed the title [WIP] Update to use Docker 17.06 EZP-27788: Update and cleanup docker config for Docker 17.06 features Aug 21, 2017
Copy link
Member

@vidarl vidarl left a comment

Choose a reason for hiding this comment

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

Looks good, but would appreciate if varnish' malloc setting is injected via environment variable as suggested


EXPOSE 80 6082

CMD ["varnishd", "-F", "-a", ":80", "-T", ":6082", "-f", "/etc/varnish/default.vcl", "-s", "malloc,256M"]
Copy link
Member

Choose a reason for hiding this comment

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

Would it not be nice if "256M" would be defined in a variable in .env ?
This is a setting which is typically customized....

Copy link
Contributor Author

Choose a reason for hiding this comment

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

true, can try to use env variables in build args.

@andrerom andrerom merged commit 10be728 into 1.7 Aug 24, 2017
@andrerom andrerom deleted the docker_17.06 branch August 24, 2017 11:28
andrerom added a commit that referenced this pull request Aug 27, 2017
Volume not currently used in prod container, and for cases where there are not css/js/bundle assets amke sure folder is there so build does not break.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants