[SOLVED] No network when running a container in Arch Linux

So after visiting the link you provided, I fixed the problem. As described there,

Blacklist interfaces
If something like Docker is creating virtual interfaces Connman may attempt to connect to one of these instead of your physical adapter if the connection drops. A simple way of avoiding this is to blacklist the interfaces you do not want to use. Connman will by default blacklist interfaces starting with “vmnet”, “vboxnet”, “virbr” and “ifb” so those need to be included as well.
Blacklisting interface names is also useful to avoid a race condition where connman may access eth# or wlan# before systemd/udev can change it to use a predictable interface name like enp4s0. Blacklisting the conventional (and unpredictable) interface prefixes makes connman wait until they are renamed.
If it does not already exist, create /etc/connman/main.conf:

[General]
NetworkInterfaceBlacklist=vmnet,vboxnet,virbr,ifb,docker,veth,eth,wlan

So I created the directory and the file, added the above lines to it, restarted connman, and now everything seems to work as expected. Thank you Jeff!!