Closed nielstron closed 2 hours ago
aarch64 is not supported for the cardano-node-ogmios image for it is not supported by the base cardano-node image. We could fancy using alternative docker images such as the ones from BlinkLabs which has supports for aarch64 / armv8 images.
One workaround for anyone stumbling accross this is running binfmt to add support for amd64 manually
$docker run --privileged --rm tonistiigi/binfmt --install amd64
installing: amd64 OK
{
"supported": [
"linux/arm64",
"linux/amd64",
"linux/arm/v7",
"linux/arm/v6"
],
"emulators": [
"python3.10",
"qemu-x86_64"
]
}
$ docker compose up
[+] Running 1/0
✔ Container opshin-pioneer-program-ogmios-1 Created 0.0s
Attaching to ogmios-1
ogmios-1 | Node configuration: NodeConfiguration {ncSocketConfig = SocketConfig {ncNodeIPv4Addr = Last {getLast = Just 0.0.0.0}, ncNodeIPv6Addr = Last {getLast = Nothing}, ncNodePortNumber = Last {getLast = Just 3000}, ncSocketPath = Last {getLast = Just "/ipc/node.socket"}}, ncConfigFile = "/config/cardano-node/config.json", ncTopologyFile = "/config/cardano-node/topology.json", ncDatabaseFile = "/db", ncProtocolFiles = ProtocolFilepaths {byronCertFile = Nothing, byronKeyFile = Nothing, shelleyKESFile = Nothing, shelleyVRFFile = Nothing, shelleyCertFile = Nothing, shelleyBulkCredsFile = Nothing}, ncValidateDB = False, ncShu
...
Albeit still no preview instance hosted by opshin since this appears to exceed the server RAM and gets OOM killed eventually
What Git revision / release tag are you using?
v6.8.0_9.2.0-preview
Do you use any client SDK? If yes, which one?
None
Describe what the problem is?
I have the following docker-compose.yaml (from the opshin-pioneer-program) and tried to host an ogmios-preview instance for new students to get up to speed quickly on a server hosted by opshin already (arm64)
https://github.com/OpShin/opshin-pioneer-program/blob/63c1336181674a15c2357f641c4329118a02b1d8/docker-compose.yaml
When starting this with docker compose up the following error gets thrown:
uname gives
What should be the expected behavior?
The docker image should spin up as expected.
If applicable, what are the logs from the server around the occurence of the problem?
See problem description