Estimated reading time: 5 minutes
After installing SQL Developer 3.2 on Mac OS 10.8.2 my disk space started running out. And kept running out. SQL Developer was constantly appending to a log file in /tmp I traced the problem to the startup.sh script for sql developer. Clients using x509 libraries from mac OS 11.0 (Big Sur) may fail to parse some certificates of sqlserver instances. This may be surfaced to the client as a generic error, like 'cancelled'. The workaround is to rotate the server certificate and recreate client certificates. Cannot modify allocated ranges in CreateConnection.
Oracle Sql Developer Macos Big Sur Pc
Docker Desktop for Mac is the Community version of Docker for Mac.You can download Docker Desktop for Mac from Docker Hub.
By downloading Docker Desktop, you agree to the terms of the Docker Software End User License Agreement and the Docker Data Processing Agreement.
What to know before you install
Relationship to Docker Machine: Installing Docker Desktop on Mac does not affect machines you created with Docker Machine. You have the option to copy containers and images from your local default
machine (if one exists) to the Docker Desktop HyperKit VM. Whenyou are running Docker Desktop, you do not need Docker Machine nodes running locally (or anywhere else). With Docker Desktop, you have a new, nativevirtualization system running (HyperKit) which takes the place of theVirtualBox system.
System requirements
Your Mac must meet the following requirements to successfully install Docker Desktop:
Mac hardware must be a 2010 or a newer model with an Intel processor, with Intel’s hardware support for memory management unit (MMU) virtualization, including Extended Page Tables (EPT) and Unrestricted Mode. You can check to see if your machine has this support by running the following command in a terminal:
sysctl kern.hv_support
If your Mac supports the Hypervisor framework, the command prints
kern.hv_support: 1
.macOS must be version 10.14 or newer. That is, Mojave, Catalina, or Big Sur. We recommend upgrading to the latest version of macOS.
If you experience any issues after upgrading your macOS to version 10.15, you must install the latest version of Docker Desktop to be compatible with this version of macOS.
Note: Docker supports Docker Desktop on the most recent versions of macOS. Docker Desktop currently supports macOS Mojave, macOS Catalina, and macOS Big Sur.
As new major versions of macOS are made generally available, Docker stops supporting the oldest version and support the newest version of macOS.
At least 4 GB of RAM.
VirtualBox prior to version 4.3.30 must not be installed as it is not compatible with Docker Desktop.
What’s included in the installer
The Docker Desktop installation includes Docker Engine, Docker CLI client, Docker Compose, Notary, Kubernetes, and Credential Helper.
Install and run Docker Desktop on Mac
Double-click
Docker.dmg
to open the installer, then drag the Docker icon to the Applications folder.Double-click
Docker.app
in the Applications folder to start Docker. (In the example below, the Applications folder is in “grid” view mode.)The Docker menu in the top status bar indicates that Docker Desktop is running, and accessible from a terminal.
If you’ve just installed the app, Docker Desktop launches the onboarding tutorial. The tutorial includes a simple exercise to build an example Docker image, run it as a container, push and save the image to Docker Hub.
Click the Docker menu () to seePreferences and other options.
Select About Docker to verify that you have the latest version.
Congratulations! You are now successfully running Docker Desktop.
If you would like to rerun the tutorial, go to the Docker Desktop menu and select Learn.
Automatic updates
Starting with Docker Desktop 3.0.0, updates to Docker Desktop will be available automatically as delta updates from the previous version.
When an update is available, Docker Desktop automatically downloads it to your machine and displays an icon to indicate the availability of a newer version. All you need to do now is to click Update and restart from the Docker menu. This installs the latest update and restarts Docker Desktop for the changes to take effect.
Uninstall Docker Desktop
To unistall Docker Desktop from your Mac:
- From the Docker menu, select Troubleshoot and then select Uninstall.
- Click Uninstall to confirm your selection.
Note: Uninstalling Docker Desktop will destroy Docker containers and images local to the machine and remove the files generated by the application.
Save and restore data
You can use the following procedure to save and restore images and container data. For example to reset your VM disk:
Use
docker save -o images.tar image1 [image2 ...]
to save any images you want to keep. See save in the Docker Engine command line reference.Use
docker export -o myContainner1.tar container1
to export containers you want to keep. See export in the Docker Engine command line reference.Uninstall the current version of Docker Desktop and install a different version (Stable or Edge), or reset your VM disk.
Use
docker load -i images.tar
to reload previously saved images. See load in the Docker Engine.Use
docker import -i myContainer1.tar
to create a filesystem image corresponding to the previously exported containers. See import in the Docker Engine.
For information on how to back up and restore data volumes, see Backup, restore, or migrate data volumes.
Where to go next
- Getting started provides an overview of Docker Desktop on Mac, basic Docker command examples, how to get help or give feedback, and links to other topics about Docker Desktop on Mac.
- Troubleshooting describes common problems, workarounds, howto run and submit diagnostics, and submit issues.
- FAQs provide answers to frequently asked questions.
- Release notes lists component updates, new features, and improvements associated with Docker Desktop releases.
- Get started with Docker provides a general Docker tutorial.
I recently updated to macOS Big Sur. There are always some growing pains when upgrading to a new operating system, and one problem I ran into was not being able to launch Oracle SQL Developer.
Oracle Sql Developer Macos Big Sur Mer
The Problem
It seems like, somewhere in the upgrade, SQL Developer (or a configuration file somewhere) lost the location of the Java JDK, typically expressed as the JAVA_HOME
environmental variable. This happened after my upgrade to macOS Big Sur. I tested this by opening my terminal app and typing echo $JAVA_HOME
, which returned nothing. So, if my system didn’t know where JAVA_HOME
was, I didn’t think SQL Developer probably knew, either.
I learned that SQL Developer should ask the user where the JAVA_HOME
is located when they first launch the app, but it never did for me. I launch the app and nothing. It bounces once or twice in the dock and then nothing.
The Solution
The first thing I did, since I had been using Java JDK 8 previously, was download and install the Java JDK 11 runtime from Oracle’s website. After I got that installed a simple edit to SQL Developer’s product configuration file was all it took to get it running.
Open your terminal app and paste in the following command to navigate to the SQL Developer product config file:
One note here is that you may have to change the 20.2.0 to the version of SQL Developer that you are using, 20.2.0 is the currect version at the time of writing this.
Now that you are in the folder, type in ls -al
to see the contents of the directory we are in. You should see a product.conf
file. We need to edit this file so SQL Developer knows where the Java JDK is located.
You can edit the file in the terminal with nano by typing in nano product.conf
if you are comfortable with that, or you can type open
in the terminal and Finder will pop up a window so you can right click the file and open it with whatever text editor you want.
On line 20 of the file you should see some text that says # SetJavaHome /path/jdk
. I created a new line under this and pasted in the following:
Make sure that the jdk-11.0.9.jdk
is the same as what you downloaded and installed from Oracle earlier. Save the file and that is it! You should now be able to launch SQL Developer normally.