Jump to content

dziekon

Members
  • Posts

    5
  • Joined

  • Last visited

Reputation Activity

  1. Like
    dziekon got a reaction from Igor in Docker on armbian!   
    For anyone struggling with Docker connectivity issues on latest Arbian minimal images, I've found solution (although, can't say if it's a good or bad solution, I'm not a sysops wizard or whatever) which does seem to work fine for my use case.
     
    Tested on "Armbian_community 24.8.0-trunk.399 Bookworm with Linux 6.6.36-current-sunxi64"
     
    By following this stackoverflow answer (https://stackoverflow.com/a/76440642/951007), I've modified netplan's default configuration file (currently "/etc/netplan/10-dhcp-all-interfaces.yaml" file) from:
    (...) all-eth-interfaces: match: name: '*' (...) to
    (...) all-eth-interfaces: match: name: 'en*' (...)  
    and restarted the entire SBC.
     
    With this change applied, docker network adapters changed their SETUP from "configuring" to "unmanaged", as it apparently should be in the first place (although please do note that other adapters have been changed as well, so proceed with caution):
    $ sudo networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 end0 ether routable configured 3 wlan0 wlan off unmanaged 4 docker0 bridge no-carrier unmanaged 5 br-xxxxxxxxxxxx bridge no-carrier unmanaged 6 br-xxxxxxxxxxxy bridge no-carrier unmanaged  
    After that, Docker was able to communicate with the outside world:
    $ docker run busybox ping -c 1 1.1.1.1 PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: seq=0 ttl=57 time=4.741 ms (...)  
    and was able to communicate with other docker-based services in the same network - in my case, a Spoolman instance was not able to communicate with Postgresql instance started using one docker compose file.
     
    ---
     
    Again, please do note that I'm no expert in this regard, so if you decide to follow this solution, I would recommend verifying whether other services (that require connectivity in any way) still work as expected.
  2. Like
    dziekon reacted to ALIGMSTEN in H616 mainlining effort   
    My humble apologies, in haste copy/paste incorrectly! have amended the example.
     
     
    Correct I've found that change to be visually appealing and closest to the 4.9 legacy kernels  
     
    Thanks, valid points, noted the on-page posting last couple, instead of correctly formatted text in attachments or links, agreed that might be easier read.
     
    Trigger Options:
    usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlo ck kbd-ctrlllock kbd-ctrlrlock usbport disk-activity disk-read disk-write ide-di sk mtd nand-disk heartbeat cpu cpu0 cpu1 cpu2 cpu3 activity default-on panic mmc 0 rfkill-any rfkill-none stmmac-0:01:link stmmac-0:01:1Gbps stmmac-0:01:100Mbps stmmac-0:01:10Mbps  
    Lets see, perhaps doing this in a 'democratic-manner' here is not the way.
     
    Merged - https://github.com/armbian/build/pull/5270
     
    As above your preferences can be altered when you build!
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines