On creating a new container (incus launch) downloads image but at 100% says unexpected EOF
You will need to provide more information for someone to be able to help you. things like
- server version
- is the server incus or incusos
- client version
- example command showing the problem
Hi Karl,
i am running ubuntu 26.04 LTS and incus 7.4 stable. incus version
Client version: 7.4
Server version: 7.4
xxxxxxx@incus:~$ incus launch images:ubuntu/24.04 name --profile=default --profile=bridgeprofile -c security.nesting=true -c boot.autostart=true
Launching name
Error: Failed instance creation: unexpected EOF
hope this helps
regards
incus monitor --pretty output while running the incus launch again in another terminal may help. Otherwise journalctl -u incus -n 300 may contain something useful.
DEBUG [2026-08-29T16:59:43Z] Connecting to a remote simplestreams server URL=“https://za.images.linuxcontainers.org”
DEBUG [2026-08-29T16:59:47Z] Acquiring lock for image fingerprint=8536a2d6fb6609d9b651597f1064d00168e5a4c0c6f2bd7e250048f69cdcf6f1
DEBUG [2026-08-29T16:59:47Z] Lock acquired for image fingerprint=8536a2d6fb6609d9b651597f1064d00168e5a4c0c6f2bd7e250048f69cdcf6f1
INFO [2026-08-29T16:59:47Z] Downloading image alias=ubuntu/26.04 fingerprint=8536a2d6fb6609d9b651597f1064d00168e5a4c0c6f2bd7e250048f69cdcf6f1 operation=f70c9f93-f905-49bd-b592-59596dd0d134 server=“https://za.images.linuxcontainers.org” trigger=/1.0/operations/f70c9f93-f905-49bd-b592-59596dd0d134
DEBUG [2026-08-29T16:59:47Z] Updated metadata for operation class=task description=“Creating instance” operation=f70c9f93-f905-49bd-b592-59596dd0d134 project=default
INFO [2026-08-29T16:59:47Z] ID: f70c9f93-f905-49bd-b592-59596dd0d134, Class: task, Description: Creating instance CreatedAt=“2026-08-29 16:59:43.147901022 +0000 UTC” Err= Location=none MayCancel=true Metadata=“map[download_progress:metadata: 100% (692B/s)]” Resources=“map[instances:[/1.0/instances/ollama]]” Status=Running StatusCode=Running UpdatedAt=“2026-08-29 16:59:47.415277023 +0000 UTC”
DEBUG [2026-08-29T16:59:50Z] Updated metadata for operation class=task description=“Creating instance” operation=f70c9f93-f905-49bd-b592-59596dd0d134 project=default
INFO [2026-08-29T16:59:50Z] ID: f70c9f93-f905-49bd-b592-59596dd0d134, Class: task, Description: Creating instance CreatedAt=“2026-08-29 16:59:43.147901022 +0000 UTC” Err= Location=none MayCancel=true Metadata=“map[download_progress:rootfs: 1% (938.57kB/s)]” Resources=“map[instances:[/1.0/instances/ollama]]” Status=Running StatusCode=Running UpdatedAt=“2026-08-29 16:59:50.064601223 +0000 UTC”
DEBUG [2026-08-29T16:59:50Z] Failure for operation class=task description=“Creating instance” err=“unexpected EOF” operation=f70c9f93-f905-49bd-b592-59596dd0d134 project=default
INFO [2026-08-29T16:59:50Z] ID: f70c9f93-f905-49bd-b592-59596dd0d134, Class: task, Description: Creating instance CreatedAt=“2026-08-29 16:59:43.147901022 +0000 UTC” Err=“unexpected EOF” Location=none MayCancel=false Metadata=“map[download_progress:rootfs: 1% (938.57kB/s)]” Resources=“map[instances:[/1.0/instances/ollama]]” Status=Failure StatusCode=Failure UpdatedAt=“2026-08-29 16:59:50.064601223 +0000 UTC”
DEBUG [2026-08-29T16:59:50Z] Event listener server handler stopped listener=b1e0f6cc-10be-4141-a029-864a950cfb02 local=/var/lib/incus/unix.socket remote=@
Jul 16 06:31:25 incus systemd[1]: Started incus.service - Incus - Daemon.
Jul 21 06:14:28 incus systemd[1]: Stopping incus.service - Incus - Daemon…
Jul 21 06:14:28 incus systemd[1]: incus.service: Deactivated successfully.
Jul 21 06:14:28 incus systemd[1]: incus.service: Unit process 225743 (dnsmasq) remains running after unit stopped.
Jul 21 06:14:28 incus systemd[1]: Stopped incus.service - Incus - Daemon.
Jul 21 06:14:28 incus systemd[1]: incus.service: Consumed 2min 37.924s CPU time over 4d 23h 43min 5.533s wall clock tim>
Jul 21 06:14:28 incus systemd[1]: incus.service: Found left-over process 225743 (dnsmasq) in control group while starti>
Jul 21 06:14:28 incus systemd[1]: incus.service: This usually indicates unclean termination of a previous run, or servi>
Jul 21 06:14:28 incus systemd[1]: Starting incus.service - Incus - Daemon…
Jul 21 06:14:31 incus dnsmasq-dhcp[225743]: router advertisement on fd42:837a:c558:311c::, old prefix for incusbr0
Jul 21 06:14:31 incus dnsmasq-dhcp[225743]: DHCPv6 stateless on fd42:837a:c558:311c::, constructed for incusbr0
Jul 21 06:14:31 incus dnsmasq-dhcp[225743]: DHCPv4-derived IPv6 names on fd42:837a:c558:311c::, constructed for incusbr0
Jul 21 06:14:31 incus dnsmasq-dhcp[225743]: router advertisement on fd42:837a:c558:311c::, constructed for incusbr0
Jul 21 06:14:31 incus dnsmasq[2195239]: started, version 2.92 cachesize 150
Jul 21 06:14:31 incus dnsmasq[2195239]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua>
Jul 21 06:14:31 incus dnsmasq-dhcp[2195239]: DHCP, IP range 10.185.1.2 – 10.185.1.254, lease time 1h
Jul 21 06:14:31 incus dnsmasq-dhcp[2195239]: DHCPv6 stateless on incusbr0
Jul 21 06:14:31 incus dnsmasq-dhcp[2195239]: DHCPv4-derived IPv6 names on incusbr0
Jul 21 06:14:31 incus dnsmasq-dhcp[2195239]: router advertisement on incusbr0
Jul 21 06:14:31 incus dnsmasq-dhcp[2195239]: DHCPv6 stateless on fd42:837a:c558:311c::, constructed for incusbr0
Jul 21 06:14:31 incus dnsmasq-dhcp[2195239]: DHCPv4-derived IPv6 names on fd42:837a:c558:311c::, constructed for incusb>
Jul 21 06:14:31 incus dnsmasq-dhcp[2195239]: router advertisement on fd42:837a:c558:311c::, constructed for incusbr0
Jul 21 06:14:31 incus dnsmasq-dhcp[2195239]: IPv6 router advertisement enabled
Jul 21 06:14:31 incus dnsmasq-dhcp[2195239]: DHCP, sockets bound exclusively to interface incusbr0
Jul 21 06:14:31 incus dnsmasq[2195239]: using only locally-known addresses for incus
Jul 21 06:14:31 incus dnsmasq[2195239]: reading /etc/resolv.conf
Jul 21 06:14:31 incus dnsmasq[2195239]: using nameserver 127.0.0.53#53
Jul 21 06:14:31 incus dnsmasq[2195239]: using only locally-known addresses for incus
Jul 21 06:14:31 incus dnsmasq[2195239]: read /etc/hosts - 8 names
Looks like the South African image server was having a bad day… It was able to serve some images (including what we used for testing) but some others were returning disk errors.
Server should behave again now.