gosu | 2D game development library for Ruby and C++ | Game Engine library

We've had some problems with Airflow in Docker so we're trying to move away from it at the moment.

Some suggestions:

1. Set the version of openpyxl to a specific version in requirements.txt
2. Add openpyxl twice to requirements.txt
3. Create a requirements.in file with your main components, and create a requirements.txt off that using pip-compile. This will add subcomponents too
4. Try specifying a python version as well

Hopefully one of these steps will help.

You need to use a font that includes those Unicode characters or Gosu's internal font rendering code will return a 0 width image for drawing that character.

A font like: https://fontlibrary.org/en/font/chess

Use Gosu's Gosu.render method

You need to put all the services under a single services key. That's also why it's plural.

Basically this error means there is no connectivity between the container and the internet but i wasn't able to figure out why this happened.

Thanks to Rwd who did mention this Github Issue in the comment section i noticed that am using an old version of docker, i was running Ubuntu 16.04 .. later i upgraded to 20.04, during the upgrade the docker repository was disabled so i ended up not upgrading docker for quiet a time.

So what i did was simply reinstalling docker :

I removed the old versions

Fixed it, I was being an idiot yesterday night.

Solution A: (In my case): Downgrade back to Docker Desktop version 4.0.0. I was using Intel Images so that's why I had to specify x86_64.

A more better solution would to change all my images be Arm64 and Intel based as well as it being compatible with Ubuntu + Mysql (currently docker Is recommending to use MariaDB for now)

However - seeing that Docker is still relatively unstable and can stop your build process at any moment, I advise anyone to update the Docker for M1 with caution!

You can directly pass integer to Gosu::Color.new to create color

You shouldn't need to run chown at all here. Leave the files owned by root (or by the host user). So long as they're world-readable the application will still be able to run; but if there's some sort of security issue or other bug, the application won't be able to accidentally overwrite its own source code.

You can then go on to simplify this even further. For most purposes, users in Unix are identified by their numeric user ID; there isn't actually a requirement that the user be listed in /etc/passwd. If you don't need to change the node user ID and you don't need to chown files, then the entrypoint script reduces to "switch user IDs and run the main script"; but then Docker can provide an alternate user ID for you via the docker run -u option. That means you don't need to install gosu either, which is a lot of the Dockerfile content.

All of this means you can reduce the Dockerfile to:

Only adding AIRFLOW_CONN_YOURCONNECTION or AIRFLOW_VAR_YOURVARIABLE is enough. Note that environment variables for connections and variables use single underscores, not double. You don't have to export environment variables in your docker-compose file, they are set upon starting containers.

For more information about environment variables and Docker Compose, see the documentation: https://docs.docker.com/compose/environment-variables/#pass-environment-variables-to-containers