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

Podman deployment issue #92

Open
aiyunyuner opened this issue Feb 22, 2025 · 3 comments
Open

Podman deployment issue #92

aiyunyuner opened this issue Feb 22, 2025 · 3 comments

Comments

@aiyunyuner
Copy link

aiyunyuner commented Feb 22, 2025

2025-02-22 18:28:48,116 INFO supervisord started with pid 4
2025-02-22 18:28:48,116 INFO supervisord started with pid 4
2025-02-22 18:28:49,118 INFO spawned: 'php-fpm' with pid 5
2025-02-22 18:28:49,118 INFO spawned: 'php-fpm' with pid 5
2025-02-22 18:28:49,119 INFO spawned: 'nginx' with pid 6
2025-02-22 18:28:49,119 INFO spawned: 'nginx' with pid 6
2025-02-22 18:28:49,120 INFO spawned: 'scheduler' with pid 7
2025-02-22 18:28:49,120 INFO spawned: 'scheduler' with pid 7
[22-Feb-2025 18:28:49] NOTICE: [pool www] 'user' directive is ignored when FPM is not running as root
[22-Feb-2025 18:28:49] NOTICE: [pool www] 'group' directive is ignored when FPM is not running as root
[22-Feb-2025 18:28:49] NOTICE: fpm is running, pid 5
[22-Feb-2025 18:28:49] NOTICE: ready to handle connections

   INFO  Running scheduled tasks every minute.

2025-02-22 18:28:50,253 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-22 18:28:50,253 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-22 18:28:50,253 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-22 18:28:50,253 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-22 18:28:50,253 INFO success: scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-22 18:28:50,253 INFO success: scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Could not open input file: artisan
Could not open input file: artisan
Could not open input file: artisan
Could not open input file: artisan
services:
  leantime:
    image: leantime/leantime:latest
    container_name: leantime
    restart: unless-stopped
    environment:
      - LEAN_DB_HOST=db
      - LEAN_DB_USER=root
      - LEAN_DB_PASSWORD=sfkhfasdfs13123
      - LEAN_DB_DATABASE=leantime
      - LEAN_DB_PORT=3306
      - PUID=0
      - PUID=0
    networks:
      - podman_default
#    volumes:
#      - ./public_userfiles:/var/www/html/public/userfiles:Z
#      - ./userfiles:/var/www/html/userfiles:Z
#      - ./plugins:/var/www/html/app/Plugins:Z
    ports:
      - 8085:80
    depends_on:
      - db
#    user: root
networks:
  podman_default:
    external: true

I encountered a problem during installation and cannot access the website.

it say ERR_CONNECTION_REFUSED

@marcelfolaron
Copy link
Contributor

Internal port is set to 8080. Try setting - 8085:8080

@marcelfolaron
Copy link
Contributor

The other thing I just noticed is that you have PUID twice. I assume once of them is supposed to be PGID

@aiyunyuner
Copy link
Author

aiyunyuner commented Feb 23, 2025

Thank you. You can access the website now, but there is no response when you click to log in. I checked and the request response is 302 Found.

Could not open input file: artisan
Could not open input file: artisan
Could not open input file: artisan
Could not open input file: artisan
127.0.0.1 -  23/Feb/2025:05:15:25 +0000 "POST /index.php" 303
127.0.0.1 -  23/Feb/2025:05:15:25 +0000 "GET /index.php" 302
127.0.0.1 -  23/Feb/2025:05:15:25 +0000 "GET /index.php" 200
127.0.0.1 -  23/Feb/2025:05:15:25 +0000 "GET /index.php" 200
127.0.0.1 -  23/Feb/2025:05:15:33 +0000 "POST /index.php" 303
127.0.0.1 -  23/Feb/2025:05:15:33 +0000 "GET /index.php" 200
127.0.0.1 -  23/Feb/2025:05:15:33 +0000 "GET /index.php" 200
127.0.0.1 -  23/Feb/2025:05:15:38 +0000 "POST /index.php" 303
127.0.0.1 -  23/Feb/2025:05:15:38 +0000 "GET /index.php" 302
127.0.0.1 -  23/Feb/2025:05:15:38 +0000 "GET /index.php" 200
127.0.0.1 -  23/Feb/2025:05:15:38 +0000 "GET /index.php" 200
Request URL: http://192.168.5.100:8085/dashboard/home
Request Method: GET
Status Code: 302 Found
Remote Address: 192.168.5.100:8085
Referrer Policy: no-referrer-when-downgrade
Request URL: http://192.168.5.100:8085/auth/login
Request Method: POST
Status Code: 303 See Other
Remote Address: 192.168.5.100:8085
Referrer Policy: no-referrer-when-downgrade
Request URL: http://192.168.5.100:8085/auth/login?redirect=dashboard%2Fhome
Request Method: GET
Status Code: 200 OK
Remote Address: 192.168.5.100:8085
Referrer Policy: no-referrer-when-downgrade
/var/www/html $ nginx -t
nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:1
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants