SDK Cannot deploy to emulator anymore

[Acorn7516]

Hello, I suddenly am unable to deploy my app to the emulator from the build engine running in docker. I think It started happenning after I had renamed my app to the allowed format by Harbour. I followed the directions in the .pro file when renaming my app and also did a few ‘cleans’ from the QtCreator UI is the rename the crux?

Searching the forum resulted in this topic but I have no custom network configuration defined.

What i’ve tried so far

• I’ve tried reinstalling the SDK
• removing the SDK and deleting all config and cache found on system and then installing it again
• removing the SDK and docker, reinstalling both
• Following the topic found and replacing the IP in dnat-emulators with 172.18.0.1 (as the 172.17.0.1 is for my docker network? see host ip addr below) and in the VM port forwards as well.

But none of this has helped and i’m at the end of my rope here so I turn to the community for help.
I have reverted all my changes and installed a fresh copy of the SDK for the logs below.

SDK Installed

➜  mitch@desktop sailfish sfdka --version                                                                                                                                                                                                                                                                                  
SDK_RELEASE=3.12.5
SDK_RELEASE_CYCLE=Stable
SDK_CONFIG_DIR=SailfishSDK
SDK_VENDOR="Jolla"

Error log

15:21:47: The process "/home/mitch/.SailfishOS/bin/sfdk" exited normally.
15:21:47: Deploying RPM package...
15:21:47: Starting: "/home/mitch/.SailfishOS/bin/sfdk" -c 'device=Sailfish OS Emulator 5.0.0.62' deploy --sdk
sfdk: [I] Options from environment: -c target=SailfishOS-5.0.0.62-i486
ssh: connect to host 10.220.220.1 port 22: Connection timed out
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(231) [sender=3.2.7]
Error running command on the build engine: Remote process crashed.
15:24:02: The process "/home/mitch/.SailfishOS/bin/sfdk" exited with code 120.
Error while building/deploying project harbour-sailrss (kit: SailfishOS-5.0.0.62-i486 (in sailfish-sdk-build-engine:mitch))
When executing step "RPM Deploy"
15:24:02: Elapsed time: 02:21.

Emulators present

➜  mitch@desktop sailfish sfdka emulator list
SailfishOS-5.0.0.62  sdk-provided,latest,default

(sfdka is my alias and resolves to sfdk binary)

Setup

Distribution: Arch Linux
Docker version 29.4.0
/etc/docker/daemon.json || $HOME/.config/docker/daemon.json: non-existent
Docker network:

➜  mitch@desktop ~ docker network ls
NETWORK ID     NAME                 DRIVER    SCOPE
5965feb7e094   bridge               bridge    local
80e1b0b37e82   host                 host      local
987a3f8fa7b5   none                 null      local
7f88a0149f82   sailfish-sdk:mitch   bridge    local

And an inspect of the sailfish-sdk network:

[
    {
        "Name": "sailfish-sdk:mitch",
        "Id": "7f88a0149f82a719b6d130c2ed85eb9bde54d16cd96db103b3036098912dd58f",
        "Created": "2026-04-12T14:50:25.102359464+02:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv4": true,
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": {},
            "Config": [
                {
                    "Subnet": "172.18.0.0/16",
                    "Gateway": "172.18.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Options": {},
        "Labels": {},
        "Containers": {
            "5974d069e8da53e7ae2312a5931ed8f3ab359ee7082f26d4898cd118da872e31": {
                "Name": "sailfish-sdk-build-engine_mitch",
                "EndpointID": "a902eccc7e699443c18e9b828f145974b9dfb53abac4a63c7a7e3628ab537c85",
                "MacAddress": "5a:4d:cf:89:4f:38",
                "IPv4Address": "172.18.0.2/16",
                "IPv6Address": ""
            }
        },
        "Status": {
            "IPAM": {
                "Subnets": {
                    "172.18.0.0/16": {
                        "IPsInUse": 4,
                        "DynamicIPsAvailable": 65532
                    }
                }
            }
        }
    }
]

Build engine ip addr output

[mersdk@5974d069e8da ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host proto kernel_lo
       valid_lft forever preferred_lft forever
2: eth0@if12: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 5a:4d:cf:89:4f:38 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 172.18.0.2/16 brd 172.18.255.255 scope global eth0
       valid_lft forever preferred_lft forever

Emulator ip addr output

[defaultuser@SDKEmulatorWayland ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:e7:70:02 brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:5a:11:00:01 brd ff:ff:ff:ff:ff:ff
    inet 10.220.220.1/24 brd 10.220.220.255 scope global eth1
       valid_lft forever preferred_lft forever

Host ip addr output

➜  mitch@desktop ~ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 38:d5:47:b9:23:e9 brd ff:ff:ff:ff:ff:ff
    altname enx38d547b923e9
    inet 192.168.1.6/24 brd 192.168.1.255 scope global noprefixroute enp6s0
       valid_lft forever preferred_lft forever
    inet6 fe80::5616:c2e:6e8f:e2cc/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 46:5e:03:0a:2d:af brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::445e:3ff:fe0a:2daf/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
5: br-7f88a0149f82: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:ef:38:41:03:3f brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global br-7f88a0149f82
       valid_lft forever preferred_lft forever
    inet6 fe80::ef:38ff:fe41:33f/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
12: vethe5eb236@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-7f88a0149f82 state UP group default
    link/ether be:04:cd:d5:3a:2b brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::bc04:cdff:fed5:3a2b/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever

So yea I hope someon from the community can help me or from Jolla even. Thanks in advance, I think I have provided everything to diagnose what is wrong but if you miss anything don’t hesitate to ask :).

[ilpianista]

Same here on Arch as well and at the end I solved it by reinstalling the SDK from scratch.

Also uninstall didn’t work at the first shot because it was trying to connect to the SDK, but after manually removing the docker image it went through.

I’m pointing the finger at the recent iptables update, but it’s just a wild guess, I’ve no proof.

[Acorn7516]

Oh yea I also suspected the iptables update (context) but I dismissed it but I am on quite an old install so I might investigate that a tad more.

Will try removing the image and adding it again to see if that makes a difference.

[hanswf]

I give the fancy search here in this forum a try (!) and got:

SDK 3.2: unable to deploy package to emulator with Docker based build engine

It should not. But your question made me realize, that there is still one piece of the puzzle missing: The NAT configuration of the emulator virtual machine. If you open the settings of the virtual machine (In Oracle VM VirtualBox Manager), you will find “Port Forwarding” in “Network” settings. There is a rule “guestssh4docker”, which quite likely has “172.17.0.1” as the host IP. You should change that to 100.64.0.1 as well.

There is also an ip address of the emulator for testing connections..

[Acorn7516]

I gave my fancy reading skills a try (!) and saw that I linked that exact post in the 2nd paragraph.

There is also an ip address of the emulator for testing connections..

What? You mean the test buttons in the IDE?