-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot start Docker Compose container after updating image #3152
Comments
You mounted whole ASF directory to external path. Either set up docker as is stated in the wiki or learn how to use docker. This is also not ASF log.txt, its just your console output. |
i'm pretty sure i set it up correctly as it was working fine before.
it's not possible to post one, it should be obvious if you read the issue. also, when creating a new issue it explicitly states:
|
Hey there! Thank you for contacting our development team at GitHub. We believe that your issue does not meet our contributing guidelines referenced during issue creation.
Reason for closing: technical difficulties using the program are not related to ASF development. Use appropriate support channel instead. Please check out our wiki if you need further help. Have a nice day! |
i disagree. i believe it's a change that happened between V5.5.3.1 and V5.5.3.2 that causes this behavior. |
You can disagree all you want - improper docker usage that through magical means worked before but no longer does is not a bug. Lack of understanding how docker works as @mrskizzex said above is not ASF bug either. We have support channels if you're interested in further explanation of how your ASF usage is wrong. As stated in contributing guidelines however, this is not the place to teach people how to use docker properly.
|
Checklist
ASF version
Latest stable release
ASF variant
docker-linux/arm64
Bug description
i attempted to update ASF with a simple
docker compose stop archisteamfarm && docker compose up archisteamfarm
from V5.5.2.3 to V6.0.0.3.Expected behavior
i expected the update to be successful.
Actual behavior
i got an error message from Docker when trying to start the container:
Steps to reproduce
docker-compose.yml
:docker compose up archisteamfarm
Possible reason/solution
V5.5.3.1 works perfectly fine.
Can you help us with this bug report?
Somehow, I can test and offer feedback, but can't code
Full log.txt recorded during reproducing the problem
BotName.json config of all affected bot instances
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: