Resolve common network configuration issues for Docker, including Mac ARM-based and locahost errors related to the Timebase components
Collector (Target Historian) Configuration
Additional Configuration (Docker Desktop)
Mac ARM-based Configuration (Docker Desktop)
You may encounter logs related to localhost or Network configurations that state a "Connection refused." If so, you will likely need to configure the network settings within the Timebase Volume files on Docker Desktop in order to historize, collect and/or visualize data.
("Connection refused" screenshot)
Collector (Target Historian) Configuration
On the Collector Config page in your web browser, select the pencil icon for the desired Target Historian. If you have more than one Target Historian, you will need to repeat these steps, if the current hostname is localhost. Change localhost to historian.
Save the changes:
Install ping
If you haven't configured your container(s) to execute a ping command, now is a good time to do so. We will use the Explorer container for the example.
We recommend installing ping in all Timebase containers, as this is a convenient way to check if the various containers are communicating with each other.
Within a Timebase container, in the "Exec" tab (see the following screenshot), execute the following commands individually:
apt-get update -y
apt-get install -y iputils-ping
then, execute ping historian as a test. You should received some packet information, if installed successfully:
NOTE: can do so for each existing container to allow the ping command as it relates to Timebase Docker Containers and the respective names of the within the YAML file.
Restart the Docker services unless you are also using the Explorer component in your architecture. If so, continue with the Explorer Configuration below to make your datasets available from the Explorer browser page as well.
Explorer Configuration
If you cannot see the desired datasets from the browser in your Explorer component, it is possible additional network configuration is necessary.
You will need to follow the previous steps (if you haven't already done so) and then go to the Docker Desktop file locations for Explorer Volume to resolve this issue.
In Docker Desktop, go to config/sources.config within in your Explorer Volume. You will right click the sources.config file to edit.
Edit the line containing "Host": " ", which is "Host": "localhost", at default. If you are using Pulse and you have configured HTTPS, it is an update to similar "Host" information, but the changes will be within the "Auth" object of the JSON file. Then, SAVE the changes to the file and RESTART your containers.
The datasets should now be available from the Explorer browser page:
NOTE: By default, explorer files for network configuration will be located at:
config/sources.config
Additional Configuration (Docker Desktop)
If you are using Docker on Windows or Linux and are having an issue with localhost, it may be helpful to update you Docker instance and utilize the "Enable host networking" feature, which was added in a recent Docker update. You can find this configuiration in the Settings when go to the Resource page and Network settings. You will need to Apply & restart Docker save the changes using the blue icon on the bottom right (see screenshot):
Mac ARM-based Configuration (Docker Desktop)
If the aformentioned steps do not work and you are using a Mac ARM-based operating system, try using your IP address instead of historian .
Support Assistance
Struggling? We are here to help and will support you. Please log your ticket and we will respond via email.