Skip to content

Installation script crashes with: "Errno::EISDIR: Is a directory @ io_fillbuf - fd:5 config/auth_provider.yml (Errno::EISDIR)" #510

@automatumkilian

Description

@automatumkilian

Environment


Description of the problem

When running the standard installation script, the process aborts after all the ENV stuff was asked with:

[+] Creating 2/2
 ✔ Container fabmanager-postgres-1  Running   0.0s 
 ✔ Container fabmanager-redis-1     Running   0.0s 
[+] Running 1/1
 ✔ Container fabmanager-elasticsearch-1  Started  0.0s 
rake aborted!
Errno::EISDIR: Is a directory @ io_fillbuf - fd:5 config/auth_provider.yml (Errno::EISDIR)
/usr/src/app/lib/provider_config.rb:7:in `initialize'
...
[ ❌ ] something went wrong while compiling the assets, exiting...

This corresponds to [issue #463](#463).
I then followed the suggested workaround from that issue (adjusted the Dockerfile, rebuilt the image locally).


Current behavior after rebuilding

Even after applying the fix and rebuilding, the container still fails to start.
This time the failure is inside supervisord due to log file permissions:

fabmanager-1     | Traceback (most recent call last):
fabmanager-1     |   File "/usr/bin/supervisord", line 33, in <module>
fabmanager-1     |     sys.exit(load_entry_point('supervisor==4.2.5', 'console_scripts', 'supervisord')())
...
fabmanager-1     | PermissionError: [Errno 13] Permission denied: '/var/log/supervisor/supervisord.log'
fabmanager-1 exited with code 1 (restarting)

The container keeps restarting with this error.


Steps to Reproduce

  1. Fresh Ubuntu 24.04 host
  2. Run installation script as far as possible
  3. Observe failure on first run (EISDIR for auth_provider.yml)
  4. Apply Dockerfile modification as described in fabmanager container keeps restarting after production install - socket.error reported errno.EACCES #463
  5. Rebuild image, run again
  6. Now the startup fails with PermissionError on /var/log/supervisor/supervisord.log

Expected Behavior

  • The installation script should complete successfully on Ubuntu 24.04.
  • Containers should start without manual intervention or permission errors.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions