edgedb/gel docker container on Mallow board

Technical Support
2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

EdgeDB/Gel Container Issue on Mallow Carrier Board

Based on your error message, the EdgeDB/Gel container is failing during bootstrap because it cannot execute the pg_config command properly. This appears to be an architecture-specific issue with the ARM64 build of the EdgeDB container on your Mallow carrier board.

Potential Solutions

1. Container Permissions and Hardware Access

Ensure your Docker container has the necessary permissions. When running containers on Torizon, you may need specific flags for hardware access (1):

# docker run --rm -it -v /var/run/dbus:/var/run/dbus -v /dev:/dev torizon/debian:$CT_TAG_DEBIAN bash

(1)

2. Memory Considerations

The issue might be related to container startup memory spikes. When starting multiple containers simultaneously, there can be significant memory overhead (2). The documentation notes that “when starting multiple containers at once, the memory spike is even greater” and recommends either reworking applications to use fewer containers or creating start dependencies between containers (2).

3. Architecture Compatibility

The error suggests an ARM64 architecture issue. This is similar to the “no matching manifest for linux/arm64/v8” errors reported in the community (3). Ensure the EdgeDB/Gel image you’re using specifically supports ARM64 architecture.

4. Container Resource Management

Consider implementing container start dependencies to avoid memory spikes during simultaneous container launches (2). You can create dependencies that make containers launch sequentially rather than all at once.

Troubleshooting Steps

  1. Check Container Architecture: Verify that the EdgeDB/Gel image supports ARM64 architecture
  2. Test with Single Container: Try running only the EdgeDB container initially to isolate the issue
  3. Monitor Memory Usage: Check if memory constraints are causing the bootstrap failure
  4. Review Container Logs: Examine detailed logs during the pg_config execution failure

Since this works on your Dahlia carrier board but not on Mallow, there might be specific hardware or configuration differences affecting container execution. The PostgreSQL configuration tool (pg_config) failure suggests either missing dependencies or architecture incompatibility in the container image.

Best regards, Toradex AI Assistant.