Docker Compose's exec command allocates a TTY by default, so you need to use the --no-TTY flag if you want to pass, for example, a file containing SQL queries to a container running MariaDB.

$ docker compose exec --no-TTY my_db_service mysql -u root -p"my_root_password" my_database_name < temp.sql

By default, at least in Ubuntu, Docker container logs will grow indefinitely (in my case up to 412 GB, thus filling up my hard drive).

To prevent this, you can create a /etc/docker/daemon.json file with the following configuration:

To access the host from inside a Docker container, you can use host.docker.internal as a hostname, at least if you're on a Windows or Mac host.

A quick and easy way to test if Docker is running correctly is to run this command:

$ docker run -p 80:80 nginx

Docker Toolbox (a "Legacy" version which is the only Docker you can use if you have Windows 10 Home and not Professional) needs an environment variable set so that docker-compose can adapt paths to Unix style, to be used in the volumes property in a docker-compose.yml file.

Go relies on the operating system for timezone data, so when you do time.LoadLocation("America/Guayaquil"), it runs code that's different in different OSes. If you use a Docker container to run your code, it's possible to include this data in the form of a .zip file.