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

Don't support memcached in containers even if it is installed #16229

Merged

Conversation

carbonin
Copy link
Member

In the monolithic image we will start memcached from the entrypoint without using systemd. The MiqMemcached code only uses systemd so that will break when we stop running systemd in the monolithic image.

This will be fine in the other container images as we don't install memcached there.

In the monolithic image we will start memcached from the entrypoint
without using systemd. The MiqMemcached code only uses systemd so
that will break when we stop running systemd in the monolithic image.

This will be fine in the other container images as we don't install
memcached there.
@miq-bot
Copy link
Member

miq-bot commented Oct 18, 2017

Checked commit carbonin@3d3f716 with ruby 2.3.3, rubocop 0.47.1, and haml-lint 0.20.0
1 file checked, 0 offenses detected
Everything looks fine. 🏆

@bdunne
Copy link
Member

bdunne commented Oct 18, 2017

Merging while red because the failures are unrelated to this change

@bdunne bdunne merged commit c036c4d into ManageIQ:master Oct 18, 2017
@bdunne bdunne added this to the Sprint 72 Ending Oct 30, 2017 milestone Oct 18, 2017
@carbonin carbonin deleted the dont_try_to_start_memcached_in_containers branch August 16, 2019 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants