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: Container Unable to Start #147
Comments
Definitely sounds like you managed to start the container as a non-root user; does the issue persist if you start without the attach/interactive options? |
Yes |
Updated /etc/sysconfig/selinux set |
There's a better solution here. In Docker 1.7+ you can tag the volumes with 'z' to tell Docker to tag the volumes so SELinux can allow Docker to access the volumes after reboot. |
Released as part of 3.0.0.1 |
* master: Adding Real ECS vnest object Properties Remove seclabel from mount options Update README.md Update ECS-GCE-MultiNode-Instructions.md remove unneed patch 3.0.0.0 Adding patch 3.0.0.1 update 3.0.0.0 patches 3.0.0.0 patches Fix for #147: mount volumes with 'z' to set SELinux flags properly. Update ecs_node_template.jinja Supply node internal IP to step2 script Update README.md Update step2_object_provisioning.py
I was able to complete the steps on https://github.com/EMCECS/ECS-CommunityEdition/blob/master/Documentation/ECS-SingleNode-Instructions.md but during my investigation of why I couldn't save a 600MB file into an s3 bucket I rebooted the host VM. Since then I can't access my container again.
I would appreciate any assistance.
The text was updated successfully, but these errors were encountered: