Add caution for no migration file creation inside the containers.

[alexdeathway]

No description provided.

[CodeStrate]

@alexdeathway can you elaborate on the issue?

[alexdeathway]

@CodeStrate The issue with third-party apps being unable to create migration files within the container is due to security restrictions, similar to the problem lqez/django-summernote#492.

There are two ways to address this issue:

1. Avoid creating migration files within the container.
2. Use a virtual environment to install and manage dependencies, ensuring they reside in a permissive working directory.

This issue involves raising an exception to inform developers about the first case.

[CodeStrate]

So if I try to make migrations I should be warned that I can not?

[alexdeathway]

You can create migrations, but issues arise when migrations for third-party apps are involved. However, the likelihood of this occurring is very slim, as I believe this happened because the third-party app was not actively maintained.

I have encountered this issue only once, but I am documenting it here for future reference in case someone else faces a similar situation.

[CodeStrate]

So let me get this straight, when we talk migrations in this context it means db correct?

So you're saying I can do it, but third party migrations may be an issue, i.e. if we use anything other than sqlite?

[alexdeathway]

Just as you create migration files using python manage.py makemigrations , third-party packages can sometimes need to create migration files as well. This can lead to issues if the user executing the command does not have permission to create files, resulting in a PermissionError: [Errno 13] Permission denied: because the migration file cannot be created in the container.

The reason we do not grant the user in the container sufficient privileges is that it could lead to significant security issues if the container is compromised by a malicious actor.

[CodeStrate]

@alexdeathway how do you propose we should solve it? We can either :

• Add warnings when user uses python manage.py makemigrations but that means, we may need to also restrict migrating via migrate
• Or disable these commands entirely inside the container

[MrARwho]

@alexdeathway

• can we raise a warning when user tries makemigration to something like letting them know to run the makemigration command locally

• copy the created migration files into the container

• apply migration inside the container

if you agree to the solution can u assign me the issue ?