#Docker mac os manager containers mac os#
#Docker mac os manager containers upgrade#
#Docker mac os manager containers full#

This post will outline the process for a basic setup using Docker.īefore moving on to the actual implementation, let me address the two questions I still receive after all these years. Which 75% of is powered by PHP.įor those reasons, I am finally making the switch to using Docker for local development with Apache, MySQL, and PHP on macOS. In fact, Apple has added a warning about using the preinstalled PHP version and plans to no longer include it in future versions of macOS.

#Docker mac os manager containers upgrade#

However, it looks like macOS Big Sur will not upgrade PHP. I held hope the next version of macOS might adopt a modern version of PHP. The primary reason was the need for a newer version of PHP. It wasn't until installing macOS Catalina that I began to move away from the preinstalled development tools I had preached for so many years.

#Docker mac os manager containers mac os#

Seems the safest bet.I know, Docker, gross right? Suppress that reaction for a few paragraphs…įor the last 8 years I've held one of the top search results for Installing Apache, PHP, and MySQL on Mac OS X. Thinking about just running Kitematic on linux.

#Docker mac os manager containers full#

Haven't been able to map ports either, but haven't tried too hard because I've had my hands full with the first two issues. If I try, the container complains that it can't find basic files which should not be externalized. Another issue is volume mapping to a folder on the host. The odd thing is, once I get a container running, from that point forward, Portainer can recreate them from scratch and start them fine. I can create/run them fine from the command-line and Kitematic, but not Portainer.

As in, I create a mysql or redis container and it won't start. The first is that it often can't start services for containers that I fire up, out of the box. I don't know what it's doing, but I have three basic problems with it. Thank you!Įdit 2: Fell out of love with Portainer. I had glanced over it earlier today, but dismissed it as an expensive 'enterprise solution' (don't ask me why maybe the way the web site looked at first glance). This should be very straight-forward to get running on a linux server. Too easy to start up and it already recognized the existing docker environment I had running on my mac. I don't know if I would be able to access Kitematic remotely (no experience with mac servers).Įdit: You guys are awesome! Portainer works perfect. I'm not sure what sort of issues I would run into. To be clear about what I like about Kitematic: easy to search for ready-made containers, easy to change ports and externalize volumes, console interface for each container.Īn alternative might be to run a mac mini server with Kitematic. What I want is to run a linux box whose only purpose is to run docker containers with web-based management that works as simple as Kitematic that I can access remotely.

Also, as I'm getting more into home automation, I'd like some of the other services to be running 24/7 to collect data, build models, etc. What I want to change is: I'd like the game servers to be available to the kids when I'm away. The problem is I take my macbook with me and they become unavailable to the rest of the family.

I use Kitematic to fire up services quickly for a variety of purposes here at home: playing minecraft or factorio with the kids, developing against a redis service, sharing files over samba, etc.