wtf is fig_bug_app?

This repository is a test case that demonstrates a bug in how Fig (an early tool for managing Docker containers) handles the .dockerignore file. The .dockerignore file is supposed to tell Docker which files and folders to exclude when building a container image, similar to how .gitignore works in version control. The problem is straightforward: when you build a Docker image directly using the docker build command, the .dockerignore rules work correctly. Files and folders listed in .dockerignore (in this case, a log folder) don't get included in the final container. However, when the same setup is run through Fig, those exclusion rules are ignored, and the log folder ends up in the container anyway. The repository's owner is asking whether this is actually how Fig is supposed to work, or if it's a genuine bug. Fig was an early orchestration tool (now incorporated into Docker Compose) that simplified managing multiple connected containers. This repository serves as evidence that Fig wasn't respecting the same exclusion rules that plain Docker honored. The test case makes it easy to reproduce the issue and compare the two behaviors side by side, you can see the file listings differ between a regular Docker build and a Fig deployment. If you're working with containerized applications, this kind of inconsistency matters because it can lead to unexpected files or sensitive data ending up in your running containers. The repository doesn't provide a fix, but rather documents the discrepancy so that developers or maintainers of Fig could investigate and address it. Today, Fig has been replaced by Docker Compose, which handles this differently, but this repo remains a useful historical record of the issue.