Skip to content
This repository has been archived by the owner on Nov 11, 2021. It is now read-only.

Unable to install containers? (even from App Templates) #34

Closed
Hukuma1 opened this issue Feb 22, 2020 · 4 comments
Closed

Unable to install containers? (even from App Templates) #34

Hukuma1 opened this issue Feb 22, 2020 · 4 comments

Comments

@Hukuma1
Copy link

Hukuma1 commented Feb 22, 2020

Problem/Motivation

Cannot install a container with default settings, even from a App Templates menu (e.g. File Browser) and receive this in log.

standard_init_linux.go:211: exec user process caused "exec format error",

Raspberry Pi 4
HassOS 3.11
Home Assistant 0.106.0b1
Portainer add-on 0.9.0

Expected behavior

Container to start up and not stop.

Actual behavior

Container stops a few seconds after starting.

Steps to reproduce

Add a new container
Run it

Proposed changes

Do not seem to know how to fix this.

@addons-assistant
Copy link

👋 Thanks for opening your first issue here! If you're reporting a 🐛 bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be useful.

@Hukuma1
Copy link
Author

Hukuma1 commented Feb 22, 2020

Tried installing same exact setup (HassOS with Portainer Add-on) on a Windows 10 VM using Hyper-V image and it seems to install containers. So main issue is isolated to Raspberry Pi (4)?

Although File Browser container now throws this error in log:

2020/02/22 21:01:26 unknown flag: --scope
Error: unknown flag: --scope

Usage:
  filebrowser [flags]
  filebrowser [command]

Available Commands:
  cmds        Command runner management utility
  config      Configuration management utility
  hash        Hashes a password
  help        Help about any command
  rules       Rules management utility
  upgrade     Upgrades an old configuration
  users       Users management utility
  version     Print the version number

Flags:
  -a, --address string    address to listen on (default "127.0.0.1")
  -b, --baseurl string    base url
  -t, --cert string       tls certificate
  -c, --config string     config file path
  -d, --database string   database path (default "./filebrowser.db")
  -h, --help              help for filebrowser
  -k, --key string        tls key
  -l, --log string        log output (default "stdout")
      --noauth            use the noauth auther when using quick setup
      --password string   hashed password for the first user when using quick config (default "admin")
  -p, --port string       port to listen on (default "8080")
  -r, --root string       root to prepend to relative paths (default ".")
      --socket string     socket to listen to (cannot be used with address, port, cert nor key flags)
      --username string   username for the first user when using quick config (default "admin")

Use "filebrowser [command] --help" for more information about a command.

@Hukuma1
Copy link
Author

Hukuma1 commented Feb 23, 2020

And now realizing the containers not running are simply not for proper architecture and must be cross compiled. Figured the Template Apps would be working for RPi machines out of the box. Closing this issue out but hopefully saves someone the time if Google brings them here.

@Hukuma1 Hukuma1 closed this as completed Feb 23, 2020
@addons-assistant
Copy link

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@addons-assistant addons-assistant bot locked as resolved and limited conversation to collaborators Mar 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant