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

is it possible to attach the container to acces the modules directories? #9

Open
skalad opened this issue Dec 20, 2014 · 2 comments
Open

Comments

@skalad
Copy link

skalad commented Dec 20, 2014

Hello, thanks for the image.

Im running my drupal int his container but by "docker attach containerid" i find no way to acces the directories of the container in order to purge some unisnatlled modules...

even with the container stopped I can not acces using "docker run -i -t ubuntu /bin/bash"

Is there any limitation with it?

Any idea to erase module direcotries as Drupan indicates to do for cleaning?

Note: a module without an uninstaller may leave tables or fields in your database. A module like this must be dealt with manually in order to completely remove it from your database,
https://www.drupal.org/node/250783

Thanks, regards

@skalad
Copy link
Author

skalad commented Dec 24, 2014

sorry... i just didnt try enought before asking.... I did it by runing the container froma the image witht he command /bin/bash doing whatever I have to do (modifiying rights or erasing modules) and then commiting it in a new image and run the new image with the command /start.sh

It works fine...

Is it correct?

Thanx for the image

regards

@Fohlen
Copy link

Fohlen commented Dec 30, 2014

Use vangrant & filecontainer to do such tasks persistently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants