Bug 1017286
Summary: | Unable to start any services or even list services using systemctl inside Fedora container | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dave Lawrence <dkl> |
Component: | docker-io | Assignee: | Lokesh Mandvekar <lsm5> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | jkeck, lsm5, mattdm, mgoldman |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-10-09 16:07:25 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dave Lawrence
2013-10-09 14:58:19 UTC
This is to be expected when entering the container that way. You are essentially running bash in "single user mode" in the container. What you want to do instead is prepare a container with mysqld installed and then run _that_ rather than /bin/bash. (I suggest making a Dockerfile which uses mattdm/fedora as the base and adds mysqld.) Or, if you want to start a container as a whole mini-OS, you could run systemd inside the container. This is not well-tested and may completely fail. (But eventually we want that working.) I'm going to close this as NOTABUG, which can sound a little harsh -- I don't mean it that way. We can continue the conversation on the fedora-cloud mailing list (or basically any other forum, really). I'm excited to see people trying this out! |