Scott W Sides

Yes I was on a machine with an old compiler. Moving to new machine cleared up the problem. Sorry to bother

Right... because the problem is on M3. I mentioned that in ticket

Yes... I dont understand how M3 could affect it either ;-) I'll give your test a try... thanks

I cant really share the docker image build files. They are proprietary and complicated (multi-stage etc). I can tell you they are built off of a centos7 image. This is...

Your simple test does work on my M3. But as you can see from my compose yaml file above... I set tty true and some others that are different from...

Not sure what you mean by 'capture exit code / state'. But here's output from docker-compose up startup ``` phoenix2:~ swsides$ docker-compose -f docker-compose-slurmMaster.yaml up -d [+] Running 1/1 ✔...

I just realized M3 is arm64... not amd64. However I'm still seeing the container exit immediately. So just to make sure 1. I'm running on mac M3 (arm64) 2. My...

The log only has the following info: phoenix2:chemistream-hpc-images swsides$ docker logs e6b45848f5e9 2024/02/22 16:51:10 Cannot get container ID As I mentioned, the docker run command is not working either. The...

Yes... I believe this is a docker thing. Now if I add "-i" to the command... then I can detach and leave the container running. This has never been the...

Ok... after more testing I think these are the essential steps. The image MUST be built with --platform=linux/arm64/v8. Then all is needed is to add entrypoint: /bin/bash to the compose.yaml...