Docker Desktop doesn’t work because Cpu is not compatible. My sysctl kern.hv_support = 0.
So I tried the solution using Docker Toolbox. Kinematic doesn’t work but Docker Quickstart terminal yes. I can start docker run hello-world and it works… Well, ok.
So I’ve installed Portainer using this in the terminal:
docker volume create portainer_data
And this:
docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest
A “docker ls” command shows portainer is up and working
But, I can’t display localhost:9443, http or https…
Could you help me to find how to display my portainer webpage ? What could I do ?
This is the webpage on the browser (Firefox and Safari) that doesn’t display. Empty page, like if there is no server.
Yes, 9443 is https. When I wrote https and http, it was to mention 9443 and 8000. I tried both and nothing happens.
The portainer container is working. I can see the status and the uptime using “docker ps”. Even after I tried all the ports, the container is still up.
How can I look at the container logs ? I have to see the file here /var/lib/docker/containers/ ?
If yes, I’ll check tomorrow morning.
That’s a kind of question to which you can find the answr pretty quickly on Google using simple keywords (or running docker ---help) like “docker containr logs”. Which is actually the command. At least in the the current version of Docker. You probably have an odler Docker which I wouldn’t recommend to use as many images could be incompatible with the docker daemon.
Check the docker version by runing the following commands:
docker info
docker version
Never even try to do anything in that folder. Of course, if Docker Tools worked as Docker Desktop, you wouldn’t have that folder on the host.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
0e3e918d0722 portainer/portainer-ce:latest "/portainer" 6 minutes ago Up 6 minutes 0.0.0.0:8000->8000/tcp, 0.0.0.0:9443->9443/tcp, 9000/tcp portainer
I can’t add the docker logs portainer because “new users” can’t post more than 2 links in a post. I’m going to find a solution…
I’m glad you found a solution. Thank you for using Code block. Please use it always when you share any terminal output, source code or error message. I will edit your prevous post as well.
Also thank you for the logs. As you cans ee, the last line is
the Portainer instance timed out for security purposes, to re-enable your Portainer instance, you will need to restart Portainer
When it happens, you just need to restart the container using `docker restart portainer" and try to access it from the browser and initialize the configuration before it times out again.
If it doesn’t help, then it is not the original problem and it just timed out because you couldn’t access it. If that is the case, I don’t know how I could help you, as I never used the tool that you do.
And as I suspected, the Docker version is quite old, so if you don’t have problem with it yet, I wouldn’t be surprised to see some issues in the near future.
I tried the “docker restart portainer” and docker ps shows portainer is running but i still can’t access to the web page https://localhost:9443.
docker ps shows this
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
2e0d6af3c978 portainer/portainer-ce:latest "/portainer" 47 hours ago Up 4 seconds 0.0.0.0:8000->8000/tcp, 0.0.0.0:9443->9443/tcp, 9000/tcp portainer
By the way, yes it’s an old version because this is docker tools. But on my iMac late 2009, what do you think is the best solution to use docker on my Mac ?
Docker Desktop is not supported. Impossible to use it because CPU is not compatible.
Docker Tools is working for docker in terminal, portainer is running in terminal but I can’t use it in the brower.
Brew ?
Another solution ?
Do you think I could use brew ? Or there is no way to use my old iMac for docker use ?
Some people have old Docker CE on Linux and start to see that some images don’t work. I know, you have a different problem, but the fact that old Docker versions could break after some time.
You can try to run another container using another port, using a different image, like nginx and if nothing works, we could assume that the tool you use is too old and can’t work in our days, or there was a bug which will not be fixed as it is not supported.
Normally I would also say that you wouldn’t be able to use Docker Desktop extensions, but it is not Docker Desktop, so you will not lose what you don’t have.
Notice that Alpine is not among those, even though the dind (Docker in Docker) image is based on Alpine, but you probably don’t want to install Docker from binaries.