`si update` fails with Docker API error
Octogonapus opened this issue · comments
What happened?
I tried update SI and encountered this error:
RUST_BACKTRACE=full si update
System Initiative Launcher is in "local" mode
Container update found for systeminit/postgres
Container update found for systeminit/otelcol
Container update found for systeminit/nats
Container update found for systeminit/jaeger
Container update found for systeminit/veritech
Container update found for systeminit/sdf
Container update found for systeminit/pinga
Container update found for systeminit/council
Container update found for systeminit/web
Launcher update found: from 20230822.165851.0-sha.6faf6e697 to 20230906.192234.0-sha.d88b9e684
Updating the containers will destroy your data!
> Are you sure you want to update the binary and the containers listed above? Yes
Error:
0: docker api: error 304 Not Modified - Not Modified
1: error 304 Not Modified - Not Modified
Location:
bin/si/src/main.rs:121
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⋮ 3 frames hidden ⋮
4: si::main::{{closure}}::h45ffedb9579a3a01
at <unknown source file>:<unknown line>
5: tokio::runtime::park::CachedParkThread::block_on::h6984b54939cef6d4
at <unknown source file>:<unknown line>
6: tokio::runtime::scheduler::multi_thread::MultiThread::block_on::h01caf9e0da255fb1
at <unknown source file>:<unknown line>
7: tokio::runtime::runtime::Runtime::block_on::h55298d632d510306
at <unknown source file>:<unknown line>
8: si::main::hfcd3c8cc689a91bd
at <unknown source file>:<unknown line>
9: std::sys_common::backtrace::__rust_begin_short_backtrace::h233a235d23abdf64
at <unknown source file>:<unknown line>
10: std::rt::lang_start::{{closure}}::h8aac612ab726957f
at <unknown source file>:<unknown line>
11: std::rt::lang_start_internal::h76f3e81e6b8f13f9
at <unknown source file>:<unknown line>
12: main<unknown>
at <unknown source file>:<unknown line>
13: __libc_start_call_main<unknown>
at <unknown source file>:<unknown line>
14: __libc_start_main@@GLIBC_2.34<unknown>
at <unknown source file>:<unknown line>
15: _start<unknown>
at <unknown source file>:<unknown line>
How can we reproduce this?
My current SI version is si 20230822.165851.0-sha.6faf6e697
.
I ran RUST_BACKTRACE=full si update
.
These are my container versions:
si status
System Initiative Launcher is in "local" mode
Launcher update found, please run `si update` to install it
Containers update found, please run `si update` to install them
Checking the status of System Initiative Software
┌────────────────────────────┬────────────┬─────────────────────────────────┐
│ Container Image ┆ State ┆ Container Version │
╞════════════════════════════╪════════════╪═════════════════════════════════╡
│ systeminit/jaeger:stable ┆ ❌ ┆ 20230817.143531.0-sha.5aa23f0e2 │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
│ systeminit/postgres:stable ┆ ❌ ┆ 20230817.143531.0-sha.5aa23f0e2 │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
│ systeminit/nats:stable ┆ ❌ ┆ 20230817.143531.0-sha.5aa23f0e2 │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
│ systeminit/otelcol:stable ┆ ❌ ┆ 20230817.143531.0-sha.5aa23f0e2 │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
│ systeminit/council:stable ┆ ❌ ┆ 20230819.004856.0-sha.ac833bf05 │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
│ systeminit/veritech:stable ┆ ❌ ┆ 20230819.004856.0-sha.ac833bf05 │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
│ systeminit/pinga:stable ┆ ❌ ┆ 20230819.004856.0-sha.ac833bf05 │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
│ systeminit/sdf:stable ┆ ❌ ┆ 20230819.004856.0-sha.ac833bf05 │
├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
│ systeminit/web:stable ┆ ❌ ┆ 20230818.225609.0-sha.120e4a227 │
└────────────────────────────┴────────────┴─────────────────────────────────┘
Operating system
Linux
Architecture
x86_64 / amd64
What browsers are you seeing the problem on?
No response
Code of Conduct
- I agree to follow this project's Code of Conduct
Additional context
Deleting and reinstalling SI is a workaround
Hi @Octogonapus! Does this happen every time you try to update, even after running the workaround?
I think the issue is due to something we fixed already. I suggest the steps for update be as follows:
si update --self
This will update the binary. Then if you run si update
it should be successful in downloading the new containers
Did that solve your issue @Octogonapus ?
I already had worked around it, so not sure how to reproduce. If you think it is already fixed, I'm fine with closing this.
Nice!