Can't start container after 0.4.1 update

[kteare]

container start ubuntu Error: unknown: "unimplemented (12): '/com.apple.containerization.sandbox.v3.SandboxContext/WriteFile' is not implemented"

[katiewasnothere]

Hi @kteare thanks for the report! Can you confirm what steps you took to uninstall any previous versions of container you had installed and then install the 0.4.1 package?

[kteare]

I initially just updated without uninstalling, But then I did the intended uninstall shell script before installing and got the same result — Best Regards Keith Teare -- +1 (650) 704-2674 (USA) +44 (7799) 927972 (UK)

…

On Aug 29, 2025, at 10:32 AM, Kathryn Baldauf ***@***.***> wrote: Hi @kteare <https://github.com/kteare> thanks for the report! Can you confirm what steps you took to uninstall any previous versions of container you had installed and then install the 0.4.1 package? — Reply to this email directly, view it on GitHub <#552 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAGOLXA62S3DSTIJQKYCVT3QCFDDAVCNFSM6AAAAACFCE3R4WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMRVHAZDGMI>. You are receiving this because you were mentioned.

[katiewasnothere]

@kteare What option did you pass to the uninstall script?

[kteare]

uninstall-container.sh -k — Best Regards Keith Teare -- +1 (650) 704-2674 (USA) +44 (7799) 927972 (UK)

…

On Aug 29, 2025, at 11:53 AM, Kathryn Baldauf ***@***.***> wrote: @kteare <https://github.com/kteare> What option did you pass to the uninstall script? — Reply to this email directly, view it on GitHub <#552 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAGOLSJKMRXGLSUDXHAR5L3QCOSZAVCNFSM6AAAAACFCE3R4WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMRVHA4DENI>. You are receiving this because you were mentioned.

[katiewasnothere]

I see. Are you trying to start a container using container version 0.4.1 when the container was created initially with a previous container version?

Can you try removing any previously created containers and retrying?

Alternatively, can you try running uninstall-container.sh -d and try again? This should require that you re-create the container you're attempting to start.

[kteare]

Understood, but the container has various settings I wanted to retain and avoid remaking its specific config. — Best Regards Keith Teare -- +1 (650) 704-2674 (USA) +44 (7799) 927972 (UK)

…

On Aug 29, 2025, at 12:30 PM, Kathryn Baldauf ***@***.***> wrote: I see. Are you trying to start a container using container version 0.4.1 when the container was created initially with a previous container version? Can you try running uninstall-container.sh -d and try again? This should require that you re-create the container you're attempting to start. — Reply to this email directly, view it on GitHub <#552 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAGOLV2OIJIZVJNZLWAK5L3QCS5FAVCNFSM6AAAAACFCE3R4WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMRVHEYDKNI>. You are receiving this because you were mentioned.

[kteare]

A full uninstall worked - but had to rebuild the container.

[katiewasnothere]

Just to clarify, do you mean re-creating the container as done with container create? That's unfortunately necessary to update to 0.4.1 since we had some breaking changes in containerization (here if you're curious).

We are not yet stable across minor releases of either container or containerization (more details here). Until then users may need to completely uninstall and recreate containers when updating to new versions of container.

[kteare]

Got it thanksSent from my iPhoneOn Aug 29, 2025, at 3:00 PM, Kathryn Baldauf ***@***.***> wrote: Just to clarify, do you mean re-creating the container as done with container create? That's unfortunately necessary to update to 0.4.1 since we had some breaking changes in containerization (here if you're curious). We are not yet stable across minor releases of either container or containerization (more details here). Until then users may need to completely uninstall and recreate containers when updating to new versions of container. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>