On Thu, Sep 16, 2021, at 6:45 AM, bob B wrote:
I am a sorry i still don't understand,
So for docker I need to run the command via "docker exec -it mailman-web" right? Does this run it as user mailman in the docker image?
Yes.
I have my archive copied from the old server and but in a location on my new docker host where it can be accessed by mailman-web image i.e /opt/mailman/web. which is the same location as /opt/mailman-web-data from inside mailman-web, right?
That is correct.
I then run the command
docker exec -it mailman-web python manage.py hyperkitty_import -l [Redacted]@[Redacted].[Redacted].org /opt/mailman-web-data/[Redacted].mbox
but I get the error:
OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "python": executable file not found in $PATH: unknown
isn't this showing that it can't find python in the docker container to run the import????
Sorry, I made a typo in the previous email. You want to run that
command with python3 instead of python.
docker exec -it mailman-web python3 manage.py hyperkitty_import -l [Redacted]@[Redacted].[Redacted].org
And turns out the typo also exists in the docs at one place. I just opened this1 report to fix it.
-- thanks, Abhilash Raj (maxking)