Internal Server Error on Mac (M1 CPU)

[wrigjz]

Hi,
We've trying to evaluation signserver so need to install ejbca, we downloaded the docker ejbca-ce on a Mac (m1 cpu) and started it according to:

docker run -it --rm -p 80:8080 -p 443:8443 -h localhost -e TLS_SETUP_ENABLED="true" keyfactor/ejbca-ce

After 2-3 mins we see the url, superadmin and superadmin password message come up.
We can connect via Firefox to the url and click through the advanced warning messages about not being trusted and then we get 'Internal Server Error'

Can anyone help?
Thanks

This loos to be where the error starts:
2023-05-21 05:13:33,393+0000 INFO [/opt/keyfactor/bin/start.sh] (process:1) * Once the P12 is downloaded, use "REMOVED" to import it. *
2023-05-21 05:13:33,393+0000 INFO [/opt/keyfactor/bin/start.sh] (process:1) **************************************************************************************
2023-05-21 05:13:33,393+0000 INFO [/opt/keyfactor/bin/start.sh] (process:1)
2023-05-21 05:14:51,148+0000 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /ejbca/enrol/keystore.jsp: java.lang.RuntimeException: java.io.IOException: Function not implemented
at [email protected]//org.xnio.nio.WatchServiceFileSystemWatcher.(WatchServiceFileSystemWatcher.java:75)
at [email protected]//org.xnio.nio.NioXnio.createFileSystemWatcher(NioXnio.java:241)
at [email protected]//io.undertow.server.handlers.resource.PathResourceManager.registerResourceChangeListener(PathResourceManager.java:275)
at [email protected]//org.wildfly.extension.undertow.deployment.ServletResourceManager.registerResourceChangeListener(ServletResourceManager.java:125)

[primetomas]

I believe it is because you are using an ARM CPU, while the EJBCA container is built with Intel. See here for another user:
https://sourceforge.net/p/ejbca/mailman/ejbca-develop/?viewmonth=202304

[wrigjz]

Thanks, now running it on Ubuntu under WSL2 on windows and all is well.

[hablutzel1]

@wrigjz , assuming that now you are using a remote Docker host running on a real AMD64 processor, just remember that you can always set up a remote Docker context (https://docs.docker.com/engine/security/protect-access/#use-ssh-to-protect-the-docker-daemon-socket) to keep executing the Docker commands from your Mac with something like:

$ docker -c my-remote-linux-on-amd64 run -it --rm -p 80:8080 -p 443:8443 -h localhost -e TLS_SETUP_ENABLED="true" keyfactor/ejbca-ce

@primetomas , to make this smoother, could you modify your build configuration to build for ARM64 as well? I think it is not even required to use a native Apple silicon computer to build the images. According to https://docs.docker.com/build/building/multi-platform/ it might be as simple as modifying some arguments to the docker buildx command:

Docker is now making it easier than ever to develop containers on, and for Arm servers and devices. Using the standard Docker tooling and processes, you can start to build, push, pull, and run images seamlessly on different compute architectures. In most cases, you don’t have to make any changes to Dockerfiles or source code to start building for Arm.

BuildKit with Buildx is designed to work well for building for multiple platforms and not only for the architecture and operating system that the user invoking the build happens to run.

When you invoke a build, you can set the --platform flag to specify the target platform for the build output, (for example, linux/amd64, linux/arm64, or darwin/amd64).

[primetomas]

There is something with some component in our build pipe-line that currently prevents cross-architecture builds. It's on the roadmap though.

[jclab-joseph]

+1
It would be nice if arm64 Linux was also supported. Arm64 EC2 is more cost-effective than amd64.

[mike-agrenius-kushner]

We're actually working on that internally  – our legacy build server doesn't support ARM, but a new one is in the near pipeline.

Cheers,
Mike