Cannot start Docker Compose container after updating image
Epikest opened this issue · comments
Checklist
- I read and understood ASF's Contributing guidelines
- I also read Setting-up and FAQ, I don't need help, this is a bug report
- This is not a duplicate of an existing issue
- I don't own more than 10 accounts in total
- I'm not using custom plugins
- This is not a question
- This is not a technical issue
- This is not ASF-ui problem
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:
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "ArchiSteamFarm": executable file not found in $PATH: unknown
Steps to reproduce
- use this
docker-compose.yml:
version: "3.8"
services:
archisteamfarm:
image: justarchi/archisteamfarm:5.5.2.3
container_name: archisteamfarm
environment:
- ASF_PATH=/asf
volumes:
- ./asf:/asf
ports:
- 1242:1242
restart: always
user: 1001:1001
pull_policy: always
volumes:
asf:
external: truedocker 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
$ doas docker compose up archisteamfarm
[+] Running 1/1
✔ archisteamfarm Pulled 0.2s
[+] Running 1/1
✔ Container archisteamfarm Recreated 0.1s
Attaching to archisteamfarm
archisteamfarm |
archisteamfarm | Host:
archisteamfarm | Version: 8.0.1
archisteamfarm | Architecture: arm64
archisteamfarm | Commit: bf5e279d92
archisteamfarm | RID: linux-arm64
archisteamfarm |
archisteamfarm | .NET SDKs installed:
archisteamfarm | No SDKs were found.
archisteamfarm |
archisteamfarm | .NET runtimes installed:
archisteamfarm | Microsoft.AspNetCore.App 8.0.1 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
archisteamfarm | Microsoft.NETCore.App 8.0.1 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
archisteamfarm |
archisteamfarm | Other architectures found:
archisteamfarm | None
archisteamfarm |
archisteamfarm | Environment variables:
archisteamfarm | Not set
archisteamfarm |
archisteamfarm | global.json file:
archisteamfarm | Not found
archisteamfarm |
archisteamfarm | Learn more:
archisteamfarm | https://aka.ms/dotnet/info
archisteamfarm |
archisteamfarm | Download .NET:
archisteamfarm | https://aka.ms/dotnet/download
archisteamfarm | 2024-03-10 01:09:02|dotnet-14|INFO|ASF|InitCore() ArchiSteamFarm V5.5.2.3 (docker/174987a0-0fa6-4d28-ba86-10cd0a99a5d3 | .NET 8.0.1; linux-arm64; Debian GNU/Linux 12 (bookworm))
archisteamfarm | 2024-03-10 01:09:02|dotnet-14|INFO|ASF|InitCore() Copyright © 2015-2024 JustArchiNET
...
$ doas docker compose up archisteamfarm
[+] Running 1/1
✔ archisteamfarm Pulled 0.2s
[+] Running 1/1
✔ Container archisteamfarm Recreated 0.1s
Attaching to archisteamfarm
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "ArchiSteamFarm": executable file not found in $PATH: unknown
### Global ASF.json config file
```json
{
"IPCPassword": "***",
"SteamOwnerID": 76561198830469843
}
BotName.json config of all affected bot instances
No response
Additional info
No response
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.
You mounted whole ASF directory to external path. Either set up docker as is stated in the wiki or learn how to use docker.
i'm pretty sure i set it up correctly as it was working fine before.
This is also not ASF log.txt, its just your console output.
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:
If no
log.txtwas recorded due to crash at the very early stage, console output should be pasted instead.
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.
Before you open an issue please review the contributing guidelines for this repository.
(...)
I understand that if my issue is not meeting contributing guidelines specified above, especially if it's a question or technical issue that is not related to ASF development in any way, then it will be closed and left unanswered.
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!
~Archi
We believe that your issue does not meet our contributing guidelines referenced during issue creation.
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.
Examples of invalid issues:
Having technical difficulties running the program in some environment, encountering expected issues caused by the user's neglect