Did the indent and that helped getting compose running:
docker compose up -d
[+] Running 2/0
⠿ Network docker_default Created 0.0s
[+] Running 1/3wershellUniversal ⠿ Network docker_default Created 0.0sux/amd64) does not match the detected host platform (linux/arm[+] Running 1/3wershellUniversal ⠿ Network docker_default Created 0.0sux/amd64) does not match the detected host platform (linux/arm[+] Running 2/3wershellUniversal ⠿ Network docker_default Created 0.0sux/amd64) does not match the detected host platform (linux/arm ⠿ Container PowershellUniversal Started 0.3s
⠸ PowershellUniversal The requested image’s platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested 0.0s
Started the Image wich resulted in a Container and the log of that container said:
Fatal error starting PowerShell Universal.
2023-03-07 08:29:28 System.IO.IOException: Function not implemented
2023-03-07 08:29:28 at System.IO.FileSystemWatcher.StartRaisingEvents()
2023-03-07 08:29:28 at System.IO.FileSystemWatcher.StartRaisingEventsIfNotDisposed()
I’m sorry for all the problems, this is not easy it seems. Not sure what I am doing wrong…
I uninstalled Docker Desktop and installed Colima.
I ran the docker build and docker run commands and there is a container running, I just cannot access it and I have no clue where to look for a log. Docker Desktop showed me the log and errors in there. As I had to de-install Docker Desktop I no longer have that luxury.
Seems this should be able to run and installing all these tools makes me think this is not the right way, else the guide from Adam would have mentioned these things as a pre-requisite.
And I must be honest here, I have no clue what I am doing in regards with Colima or Rosetta and which would maybe help out.
@adam : can you help here? Is this docker image supposed to be able to run on MacOS as host? The error messages posted above all call out some function/method not being available.
Above all I want to avoid wasting everybody’s time if this image was never supposed to run on MacOS.
@Steven you need docker desktop as well as colima. Colima uses docker and is just the runtime for the docker containers… I am running psu on a M1 mac using docker and Colima.
Process:
Install docker and docker desktop.
Install Colima.
Start colima. colima start
Start the psu docker container.
I typically use this method when images are not compatible with the m1 chip, but see if this works for you.
System Version: macOS 13.2.1 (22D68)
Chip: Apple M1 Pro
colima list
PROFILE STATUS ARCH CPUS MEMORY DISK RUNTIME ADDRESS
default Running x86_64 2 4GiB 60GiB docker
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ad3117b52f63 universal-persistent:latest "./Universal/Univers…" About a minute ago Up About a minute 0.0.0.0:5000->5000/tcp, :::5000->5000/tcp powershelluniversal
I did that, and I have no idea if it worked or what the error might be if not working.
The Container seems to be running but I cannot check or do not know how to check.
I did do this command as I got an error running the image:
lsof -iTCP:6002 -iUDP:6002 -n -P
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
ssh 3058 stevenspierenburg 16u IPv4 0x670cdcec06e29365 0t0 TCP *:6002 (LISTEN)
No idea why this port 6002 is all of a sudden “ssh”?
docker: Cannot connect to the Docker daemon at unix:///Users/stevenspierenburg/.colima/default/docker.sock. Is the docker daemon running?.
See ‘docker run --help’.
I have a feeling I am going downhill and getting bad results. This is supposed to be easy, if I understood this right, but this is increasingly more difficult. Did I break my system? Do I need to undo what I installed or set?
I’m sorry, I must sound like a whiner and in a way I am. This is so frustrating and makes me think: am I too invested in this PSU as solution? Should I look around and find another product that fights me a little less? So I must sound like a whiner and I apologise for it.
And before I buy this product, I have some doubts about these issues and start to wonder if support is better if paid for it. I suppose it is, makes sense. But buying a product where I face immediate blockades and no resolution in sight does not make for a good start.
Once you have your M1 chip issues sorted, that compose script I posted should work.
According to your build config above you are exposing port 5000 which is correct, however when you go to run your built container you pipe port 6002 to 6002 which is not exposed.
Please note that your build is only rebuilding whatever Adam has already built in his published docker images.
I can also see that your storage is mounted to psudata. Have you created a storage mount in docker called psudata? Otherwise, you should be able to replace that with a folder path.
I thought I had to stay away from the EXPOSE in the dockerfile because Adam already ‘did something’?
Can you tell me what is the right way to start this all? Do I need a dockerfile? Do I need to assign ports?
And storage, no idea. I want to start simple, effectively have it working and then work my way up to more complex issues, like storage. We can omit if that is better?
I cannot use port 5000 as that is already claimed by a core process in MacOS.
