Pitfalls with Oracle 11g XE and Docker on Mac OS. The swap space problem and how to fix it. Posted by Ottmar Gobrecht on March 21. I use currently a Node.js based proxy server running directly on my Mac OS, because I need a webserver there anyway. Happy installing:-) Ottmar. How to Install Node.js and npm on Mac OS with Homebrew. The easiest way to install node.js and npm is with the Homebrew package manager, which means first you will need to install Homebrew on the Mac first if you have not done so already. It’s always a good idea to update Homebrew before installing a Homebrew package, so run the following.
Estimated reading time: 7 minutesYou can run Compose on macOS, Windows, and 64-bit Linux.
Prerequisites
Docker Compose relies on Docker Engine for any meaningful work, so make sure youhave Docker Engine installed either locally or remote, depending on your setup.
On desktop systems like Docker Desktop for Mac and Windows, Docker Compose isincluded as part of those desktop installs.
On Linux systems, first install theDockerfor your OS as described on the Get Docker page, then come back here forinstructions on installing Compose onLinux systems.
To run Compose as a non-root user, see Manage Docker as a non-root user.
Install Compose
Follow the instructions below to install Compose on Mac, Windows, Windows Server2016, or Linux systems, or find out about alternatives like using the pipPython package manager or installing Compose as a container.
Install a different version
The instructions below outline installation of the current stable release(v1.25.4) of Compose. To install a different version ofCompose, replace the given release number with the one that you want. Composereleases are also listed and available for direct download on theCompose repository release page on GitHub.To install a pre-release of Compose, refer to the install pre-release buildssection.
Install Compose on macOS
Docker Desktop for Mac and Docker Toolbox already include Compose alongwith other Docker apps, so Mac users do not need to install Compose separately.Docker install instructions for these are here:
- Get Docker Toolbox (for older systems)
Install Compose on Windows desktop systems
Docker Desktop for Windows and Docker Toolbox already include Composealong with other Docker apps, so most Windows users do not need toinstall Compose separately. Docker install instructions for these are here:
- Get Docker Toolbox (for older systems)
If you are running the Docker daemon and client directly on MicrosoftWindows Server, follow the instructions in the Windows Server tab.
Install Compose on Windows Server
Follow these instructions if you are running the Docker daemon and client directlyon Microsoft Windows Server with Docker Engine - Enterprise,and want to install Docker Compose.
Start an “elevated” PowerShell (run it as administrator).Search for PowerShell, right-click, and chooseRun as administrator. When asked if you want to allow this appto make changes to your device, click Yes.
In PowerShell, since GitHub now requires TLS1.2, run the following:
Then run the following command to download the current stable release ofCompose (v1.25.4):
Note: On Windows Server 2019, you can add the Compose executable to $Env:ProgramFilesDocker. Because this directory is registered in the system PATH, you can run the docker-compose --version command on the subsequent step with no additional configuration.
Test the installation.
Install Compose on Linux systems
On Linux, you can download the Docker Compose binary from the Composerepository release page on GitHub. Follow the instructions from the link, which involverunning the curl command in your terminal to download the binaries. These step-by-step instructions are also included below.
For alpine, the following dependency packages are needed:py-pip, python-dev, libffi-dev, openssl-dev, gcc, libc-dev, and make.
Run this command to download the current stable release of Docker Compose:
To install a different version of Compose, substitute
1.25.4with the version of Compose you want to use.If you have problems installing with
curl, seeAlternative Install Options tab above.Apply executable permissions to the binary:
Note: If the command docker-compose fails after installation, check your path.You can also create a symbolic link to /usr/bin or any other directory in your path.
For example:
Optionally, install command completion for the
bashandzshshell.Test the installation.
Alternative install options
Install using pip
For alpine, the following dependency packages are needed:py-pip, python-dev, libffi-dev, openssl-dev, gcc, libc-dev, and make.
Compose can be installed frompypi using pip. If you installusing pip, we recommend that you use avirtualenv because many operatingsystems have python system packages that conflict with docker-composedependencies. See the virtualenvtutorial to getstarted.
If you are not using virtualenv,
pip version 6.0 or greater is required.
Install as a container
Compose can also be run inside a container, from a small bash script wrapper. Toinstall compose as a container run this command:
Install pre-release builds
If you’re interested in trying out a pre-release build, you can download releasecandidates from the Compose repository release page on GitHub.Follow the instructions from the link, which involves running the curlMatica drivers for mac. commandin your terminal to download the binaries.
Pre-releases built from the “master” branch are also available for download athttps://dl.bintray.com/docker-compose/master/.
Pre-release builds allow you to try out new features before they are released,but may be less stable.
Upgrading
If you’re upgrading from Compose 1.2 or earlier, remove ormigrate your existing containers after upgrading Compose. This is because, as ofversion 1.3, Compose uses Docker labels to keep track of containers, and yourcontainers need to be recreated to add the labels.
If Compose detects containers that were created without labels, it refusesto run, so that you don’t end up with two sets of them. If you want to keep usingyour existing containers (for example, because they have data volumes you wantto preserve), you can use Compose 1.5.x to migrate them with the followingcommand:
Alternatively, if you’re not worried about keeping them, you can remove them.Compose just creates new ones.
Uninstallation
To uninstall Docker Compose if you installed using curl:
To uninstall Docker Compose if you installed using pip:
Got a “Permission denied” error?
If you get a “Permission denied” error using either of the abovemethods, you probably do not have the proper permissions to removedocker-compose. To force the removal, prepend sudo to either of the abovecommands and run again.
Where to go next
compose, orchestration, install, installation, docker, documentation
; Date: 2016-10-16 15:41 Tags: Mac OS X
A key step for upgrading the disk on a MacBook Pro is to install a new operating system on the new drive, and then use Migration Assistant to copy over the old data. Depending on how you went about the work, installing Mac OS X on the new system may give you a message: OS X could not be installed on your computer. No packages were eligible for install.
This is what it looks like in the installer. Upon seeing this I went 'HUH?' because the installation was from a thumb drive I'd used many times to install Mac OS X (El Capitan) successfully.
The above image came from an attempt to install El Capitan. I just got the following message, macOS could not be installed on your computer, while trying to install macOS High Sierra.
In both cases there was the same cause. In the El Capitan case, as I say in the next paragraph, the hardware clock had reset to zero because it did not have a battery pack. In the High Sierra case, I had performed a hardware reset of the computer in an attempt to fix a bootup problem. I had found advice to disconnect the battery, the power supply, then hold down the power key for a few moments. In both cases the hardware clock had been reset to zero, and macOS refused to boot.
After some yahoogling (duckduckgoing) I came across a simple solution. This particular computer had been running with no battery, and therefore the hardware clock was reset to zero, and Mac OS X had a test against that condition.
We've discussed elsewhere the process to install Mac OS X onto a computer, and transfer information from an old drive. It's during that process when the above message appears. A couple steps prior is where you can take action to correct the problem.
At this step, click on Terminal ..
Then change the operating system date.
When running this particular Terminal session, you are ROOT meaning you can change anything on the computer. Normally we type 'date' at the command line just to find out the current day/month/year/time. But, the date command can be used to change the time registered in the system clock.
As I said above, for this particular computer the system clock had been reset to zero because the battery pack had been changed. In fact, the computer had run without a battery for many months because the old battery had gone bad.
As you see on the screen, the date had been January 1, 2001. I then changed the system date to the current time as of the writing of this posting.
To understand the second command, go to a terminal window and type 'man date'.
In the synopsis section you'll see this as an option for the 'date' command:
That's a little obtuse, but further down the manpage is this key:
In other words, the date code for this purpose is month-day-hour-minutes-year .. hence, that's what I entered and it changed the system date to match.
Afterward I closed the Terminal window and was able to successfully install Mac OS X on the computer.
Please enable JavaScript to view the comments powered by Disqus.