Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find a DinD (Docker in Docker) image which supports bazel #194

Open
angeloprobst opened this issue Jan 22, 2025 · 0 comments
Open

Find a DinD (Docker in Docker) image which supports bazel #194

angeloprobst opened this issue Jan 22, 2025 · 0 comments
Assignees
Labels
Future Work Required Used to mark tickets closed with `TODO` or `FIXME` in the merged code.
Milestone

Comments

@angeloprobst
Copy link
Collaborator

angeloprobst commented Jan 22, 2025

Currently, we are using an Alpine Linux DinD image as base to build the container that runs in our OpenFaaS.

In order to support it, we need to build our code in an Alpine Building Image because Alpine Linux does not work with the glibc (the GNU C Library), like Ubuntu and most distros do. Instead, it uses the Musl C Library. So, it's not possible to build the packages using a Ubuntu Building Image and then deploy those packages in an Alpine based container. That's why a "special build" in an Alpine Building Image is required, just to produce Alpine-compatible packages.

However, once bazel became our default building tool, since we decided to turn the das repository our mono-repo, I faced some issues when trying to build the packages in an Alpine image. And found out that Alpine is not officially supported by bazel, so there is no guarantee they will work together.

As supporting OpenFaaS is not a high priority (as of January 2025), we decided to postpone the efforts to make it work. A possible solution is to build our own DinD image based on Ubuntu (@eddiebrissow already did this in a recent past, in this same project).

For more details: https://github.com/singnet/das-serverless-functions/blob/master/Dockerfile

@angeloprobst angeloprobst added the Future Work Required Used to mark tickets closed with `TODO` or `FIXME` in the merged code. label Jan 22, 2025
@angeloprobst angeloprobst added this to the Query Engine milestone Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Future Work Required Used to mark tickets closed with `TODO` or `FIXME` in the merged code.
Projects
None yet
Development

No branches or pull requests

2 participants