ftp.py | FTP Server based on Python | FTP library

Do you mean:

open(file_path) opens the file in text mode, so it'll treat the binary .mp4 file as if it was UTF8-encoded text.

You should open it in binary mode instead: open(file_path, 'rb').

The Alpine base images are based on a compact tool set called BusyBox and when you run crond here you're getting the BusyBox cron and not any other implementation. Its documentation is a little sparse, but if you look at the crond source (in C) what you'll find is that there is not any redirection at all when it goes to run a job (see the non-sendmail version of start_one_job); the job's stdout and stderr are crond's stdout and stderr. In Docker, since crond is the container primary process, that in turn becomes the container's output stream.

Anything that shows up in docker logs definitionally went to stdout or stderr or the container's main process. If this cron implementation wrote your job's output directly there, there's nothing wrong or insecure with taking advantage of that.

In heavier-weight container orchestration systems, there is some way to run a container on a schedule (Kubernetes CronJobs, Nomad periodic jobs). You might find it easier and more consistent with these systems to set up a container that runs your job once and then exits, and then to set up the host's cron to run your container (necessarily, as root).

Well, after my crash on boot this morning (got an initramfs prompt, which led me to run fsck while in grub), I decided to just go ahead an reinstall my OS. I reinstalled Ansible using apt, ran the playbook with ansible-playbook .yml and it completed without the errors. This is not a solution, per se, since I obviously had other problems going on, but the python error is gone.

The code is actually for progressbar2 library.

Its ProgressBar class implements __iadd__.

The version of paramiko (1.15.2) isn't compatible with python 3.7. Use a newer version. It uses the async keyword which is reserved as argument in a function call.

If you look at the latest version, you'll see that this particular line of code is now using async_.

You should always use the same version of python on your local machine as on production to spot these errors earlier.

I also suggest you look at some of the other dependencies, your version of gunicorn is also more than 5 years old, it contains security vulnerabilities, so may some other (old) packages you're using.

Finally, use pip freeze to compare what's installed in your local virtualenv compared to requirements.txt. And make sure they are the same!

You're right, this deprecation warning is from ftputil.

ftputil uses the Python warnings module to show this warning. The warnings module not only outputs warnings (by default to stderr), but also offers ways to control which warnings are actually shown (see The Warnings Filter and Temporarily Suppressing Warnings).

You can suppress the ftputil warning with

For anyone looking for an answer, the issue was that implicit FTPS connections need the socket to be ssl wrapped automatically.I used the below piece of code written by George Leslie-Waksman

Your server is using a keyboard-interactive authentication, not a simple password authentication.

Normally Paramiko is smart enough to fallback to the keyboard-interactive authentication, when the password authentication fails and the keyboard-interactive prompt has one field only (likely a password).

The problem is that your server behaves, as if the password authentication succeeded.

You can explicitly make Paramiko try the keyboard-interactive authentication using this code: