Skip to content
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

Closed
8 tasks done
Epikest opened this issue Mar 10, 2024 · 5 comments
Closed
8 tasks done

Cannot start Docker Compose container after updating image #3152

Epikest opened this issue Mar 10, 2024 · 5 comments
Labels
🗑️ Invalid Issues marked with this label are invalid - they should not be posted here in the first place. 🐍 Not a bug Issues marked with this label indicate that given behaviour is intended to happen - not a bug. ❌ Won't fix Issues marked with this label are not considered and they won't receive any development action.

Comments

@Epikest
Copy link

Epikest commented Mar 10, 2024

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:

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

  1. 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: true
  1. 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

$ 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

@Epikest Epikest added 🐛 Bug Issues marked with this label indicate unintended program behaviour that needs correction. 👀 Evaluation Issues marked with this label are currently being evaluated if they're going to be considered. labels Mar 10, 2024
@Epikest Epikest changed the title ASF cannot start Docker Compose container after updating image Cannot start Docker Compose container after updating image Mar 10, 2024
@mrskizzex
Copy link

mrskizzex commented Mar 10, 2024

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.

@Epikest
Copy link
Author

Epikest commented Mar 10, 2024

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.txt was recorded due to crash at the very early stage, console output should be pasted instead.

@JustArchi
Copy link
Member

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

@JustArchi JustArchi closed this as not planned Won't fix, can't repro, duplicate, stale Mar 10, 2024
@JustArchi JustArchi added 🗑️ Invalid Issues marked with this label are invalid - they should not be posted here in the first place. ❌ Won't fix Issues marked with this label are not considered and they won't receive any development action. 🐍 Not a bug Issues marked with this label indicate that given behaviour is intended to happen - not a bug. and removed 🐛 Bug Issues marked with this label indicate unintended program behaviour that needs correction. 👀 Evaluation Issues marked with this label are currently being evaluated if they're going to be considered. labels Mar 10, 2024
@Epikest
Copy link
Author

Epikest commented Mar 10, 2024

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.

@JustArchi
Copy link
Member

JustArchi commented Mar 10, 2024

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

#3154

@JustArchiNET JustArchiNET locked as resolved and limited conversation to collaborators Mar 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🗑️ Invalid Issues marked with this label are invalid - they should not be posted here in the first place. 🐍 Not a bug Issues marked with this label indicate that given behaviour is intended to happen - not a bug. ❌ Won't fix Issues marked with this label are not considered and they won't receive any development action.
Projects
None yet
Development

No branches or pull requests

3 participants