Replies: 4 comments 3 replies
|
Hi @PunkFleet, apologies for the delay in responding! If you still have that container around, do you see anything unusual in either of: container logs openwrt
container logs --boot openwrtIf you've created a new container since, do you still see the same problem if you run a sequence like: container run --name openwrt ...
container system stop
container system start
container start openwrt |
1 reply
There are too many similar log entries here, so I have extracted some of the most recent ones. In v0.2.0, I used the amd64 image, and everything worked fine. |
|
You're trying to restart the container like this, correct? container start openwrtDo you get any error output from the command? Or does the container just stay in the stopped state? If you follow the system logs using |
1 reply
Yup, It just stays in a stopped state with no error messages. Then I uninstalled it without retaining any data and reinstalled it, and now there are no problems when starting up.
It will freeze and likewise not provide any output information. |
|
@PunkFleet Do you believe that there's anything special about that particular container/image that causes it not to start after the upgrade? It looks like in your most recent post the container is running. Does Could you describe the procedure for reproducing the issue? I could try downgrading my setup to 0.2.0 and seeing if the same happens on my system if you can provide the steps. |
1 reply
I eventually discovered that my issue was due to repeated installations: |
|
That's an interesting discovery! The brew package is third-party maintained so it's not something we've given consideration to when troubleshooting, but if overlapping installs is what triggers the problem, then figuring out the root cause and how to fix or at least automatically diagnose it would be valuable. We (as in code owners) don't have the cycles right now to hunt this down, but if you can figure out a way to reliably reproduce the failure on 0.4.1 (looks like the homebrew formula is already updated), please create a bug issue for it. Thanks for your diligence on this, and I'm glad you're up and running again. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I upgraded from 0.2.0 to 0.3.0 using the command
uninstall-container.sh -k.However, the original container cannot be started by
container exec -it openwrtaftercontainer start openwrt. Here is the log:All reactions