This document mainly provides related issues and solutions for Baetyl deployment and startup in various platforms.

Q1: Prompt missing startup dependency configuration item when starting Baetyl in docker container mode.


Suggested Solution: As shown in the above picture, Baetyl startup lacks configuration dependency files, refer to GitHub-Baetyl example folder(the location is etc/baetyl/conf.yml).

Q2: Execute the command docker info get the following result on Ubuntu/Debian: “WARNING: No swap limit support”

Suggested Solution:

  1. Open /etc/default/grub with your favorite text editor. Make sure the following lines are commented out or add them if they don’t exist:
GRUB_CMDLINE_LINUX=”cgroup_enable=memory swapaccount=1”
  1. Save and exit and then run: sudo update-grub and reboot.

NOTE: If you got some error when you execute step2, it may be that the grub setting is incorrect. Please repeat steps 1 and 2.

Q3: Found “WARNING: Your kernel does not support swap limit capabilities. Limitation discarded” when Baetyl start.

Suggested Solution: Refer to Q2.

Q4: Found “Got permission denied while trying to connect to the docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.38/images/json: dial unix /var/run/docker.sock: connect: permission denied” when Baetyl start.

Suggested Solution: Add the docker group if it doesn’t already exist:

sudo groupadd docker

Add the current user to the docker group:

sudo usermod -aG docker ${USER}
su - ${USER}

Q5: Found “Cannot connect to the docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?” when Baetyl start.

Suggested Solution: If you still report this issue after the solution of Q4 solution is executed, restart the docker service.

For example, execute the following command on CentOS:

systemctl start docker

Q6: Found “failed to create master: Error response from daemon: client version 1.39 is too new. Maximum supported API version is 1.38” when Baetyl start.

Suggested Solution:

  • If the version of Baetyl is equal to or greater than 1.0.0, to set API version in the configuration file (etc/baetyl/conf.yml) of Baetyl:
  api_version: 1.38
  • If less than 1.0.0, to set environment variable DOCKER_API_VERSION=1.38, for example:
sudo vim ~/.bash_profile
source ~/.bash_profile

Q7: How does Baetyl connect to NB-IOT network?

Suggested Solution: NB-IoT is a network standard similar to 2/3/4G with low bandwidth and low power consumption. NB-IoT supports TCP-based MQTT protocol, so you can use NB-IoT card to connect to Baidu Cloud IotHub, deploy Baetyl application and communicate with BIE Cloud Management Suite. However, among the three major operators in China, Telecom have imposed whitelist restrictions on their NB cards, and only allow to connect to Telecom Cloud service IP. Therefore, only Mobile NB cards and Unicom NB cards can be used to connect to Baidu Cloud service.

Q8: Does Baetyl support to push data to Kafka?

Suggested Solution: Support, you can refer to How to write a python script for python runtime, and subscribe messages from the local Hub module and writing them to Kafka service. Besides, you can also refer to How to develop a customize module for Baetyl, which subscribes message from the local Hub module and then writes it to Kafka.

Q9: What are the ways to change Baetyl configurations? Can I only make configuration changes through the BIE Cloud Management Suite?

Suggested Solution: Currently, we recommend changing configurations through the BIE Cloud Management Suite, but you can also manually change the configuration file on the core device and then restart Baetyl to take effect.

Q10: I download MQTTBox client, extract it to a directory, and copy/move the executable file MQTTBox to /usr/local/bin(other directory is similar, such as /usr/bin, /bin, /usr/sbin, etc.). But it reports an error of “error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directorywhenMQTTBox” start.

Suggested Solution: As above description, this is because the lack of libgconf-2.so.4 library when MQTTBox start, and the recommended use is as follows:

  • Step 1: Download and extract the MQTTBox software package;
  • Step 2: cd /pat/to/MQTTBox/directory and sudo chmod +x MQTTBox;
  • Step 3: sudo ln -s /path/to/MQTTBox /usr/local/bin/MQTTBox;
  • Step 4: Open terminal and execute the command MQTTBox.

Q11: localfunc can’t process the message, check funclog has the following error message:

level=error msg=”failed to create new client” dispatcher=mqtt error=”dial tcp refused”

Suggested Solution: If you are using the BIE Cloud Management Suite to deliver the configuration, there are a few points to note:

  1. Cloud delivery configuration currently only supports container mode.
  2. If the configuration is sent in the cloud, the hub address configured in localfunc should be localhub instead of

According to the above information, the actual error is judged, and the configuration is delivered from the cloud as needed, or by referring to Configuration Analysis Document for verification and configuration.

Q12: How can i use BIE Cloud Management Suite with CFC(Cloud Function Compute)?

Suggested Solution:

  1. Make sure your BIE configuration and CFC functions in the same region, such as beijing/guangzhou.
  2. Make sure your CFC functions are published.
  3. Select CFC function template when volume create, more detailed contents please refer to How-to-apply-volume-in-the-right-way

Q13: What‘s the relationship between the parameter ports and the parameter listen which in the hub configuration file?

Suggested Solution:

  1. ports: Port exposed configuration in docker container mode.
  2. listen: Which address the hub module will listen on. In docker container mode, it’s means container address. In native process mode, it’s means host address.
  3. By referring to Configuration Analysis Document

Q14: How to process data in the cloud platform after message send to Baidu IoT Hub by Baetyl?

Suggested Solution: In the cloud platform, the Rule Engine can be used to transmit data to other cloud services, such as CFC(Cloud Function Compute), TSDB.

Q15: How to connect the Device management of Baidu IoT Hub?

Suggested Solution: The Device management of Baidu IoT Hub does not support ssl authentication. As a temporary solution, you can configure Remote Feature to connect the Device management with username and password authentication manually.

Q16: If I don’t want to lose messages and want to ensure all messages are synchronized to cloud, how can I do?

Suggested Solution:

You must meet the following 2 conditions:

  • To make sure messages will be persist in local disk which are sent to local hub, the topic’s QoS must be set to 1.
  • To make sure messages will be sent to cloud successful, the QoS of rules configuration of Remote module must be set to 1, which includes remote sub’s QoS and the pub’s QoS. By referring to Configuration Analysis Document

Q17: After the configuration is sent from the cloud to the edge, the default startup mode is docker container mode. After modifying mode: native in etc/baetyl/conf.yml the startup error is similar to the following: “failed to update system: open /Users/ Xxx/baetyl_native/var/run/baetyl/services/agent/lib/baetyl/hub.baidubce.com/baetyl/baetyl-agent:latest/package.yml: no such file or directory”.

Suggested Solution: At present, our cloud management does not support the process mode. If you need to start Baetyl in process mode locally, please refer to the configuration content in example/native and execute the command make install-native. Install and start by process with the command sudo baetyl start.

Q18: There is a similar error when downloading the image: “error=”Error response from daemon: Get https://hub.baidubce.com/v2/: x509: failed to load system roots and no roots provided” baetyl= Master”.

Suggested Solution: This is because the ca-certificates package is missing from the system and can be installed to solve this problem. For example, if the host system is Debian, you can use the following command to install it:

sudo apt-get update
sudo apt-get install ca-certificates

For other systems, please check the relevant installation operations yourself.