Skip to content

Migration isolation failing even with script saying version is higher #627

Closed

Description

@opheus2

Steps To Reproduce

Enabling AUTORUN_LARAVEL_MIGRATION_ISOLATION on a laravel 11 on the latest image
Throws error

Outcome

Image

What did you expect?

Migrations should run

What happened instead?

Migrations not running

Affected Docker Images

serversideup/php:8.4-fpm-nginx-alpine

Anything else?

No response

Activity

  1. jaydrogers commented on Dec 5, 2025

    @jaydrogers
    Member

    Looking into this now. If you're available for a quick response to this question, it will be very helpful.

    I am able to replicate this but here's my question:

    👉 Is this happening to you on first provision (where it's creating the database for the first time?)

    I am seeing this error:

      Illuminate\Database\QueryException 
    
      SQLSTATE[42P01]: Undefined table: 7 ERROR:  relation "cache_locks" does not exist
    LINE 1: update "cache_locks" set "owner" = $1, "expiration" = $2 whe...
                   ^ (Connection: pgsql, SQL: update "cache_locks" set "owner" = r10EHDELhgPuJVQj, "expiration" = 1764960310 where "key" = laravel-cache-framework/command-migrate and ("owner" = r10EHDELhgPuJVQj or "expiration" <= 1764956710))
    
      at vendor/laravel/framework/src/Illuminate/Database/Connection.php:824
        820▕                     $this->getName(), $query, $this->prepareBindings($bindings), $e
        821▕                 );
        822▕             }
        823▕ 
      ➜ 824▕             throw new QueryException(
        825▕                 $this->getName(), $query, $this->prepareBindings($bindings), $e
        826▕             );
        827▕         }
        828▕     }
    
          +18 vendor frames 
    

    If you want further output in your case

    You can set AUTORUN_DEBUG=true to get more output why it's failing.

  2. added and removed
    🧐 Bug: Needs ConfirmationSomething isn't working, but needs to be confirmed by a team member.
    on Dec 5, 2025
  3. jaydrogers commented on Dec 5, 2025

    @jaydrogers
    Member

    I believe this should be fixed in #628. You can test it by using this test image (once this build is done):

    serversideup/php-dev:628-8.4-fpm-nginx-alpine
    

    How I confirmed this fix

    I used these variables:

    AUTORUN_ENABLED: true
    AUTORUN_LARAVEL_MIGRATION_ISOLATION: true
    AUTORUN_DEBUG: true
    

    My results

    ✅ It worked

    Image

    Next Steps

    Let me know if my test image solves your problem and I will get this merged 👍

  4. opheus2 commented on Dec 23, 2025

    @opheus2
    Author

    Hey @jaydrogers sorry I just got back and testing now.

    Image it's not working

    Edit:
    Is it not better to remove the laravel version check? If it's not past that version, wouldn't the command just fail, or is it destructive?

  5. jaydrogers commented on Jan 16, 2026

    @jaydrogers
    Member

    Could you try running this again?

    Make sure to pull the latest image:

    serversideup/php-dev:628-8.4-fpm-nginx-alpine
    

    If you get back to me soon enough and this is a good fix, then this will be made available in the next release.

  6. moved this from Todo to In Progress in serversideup/php: v4.3on Jan 17, 2026
  7. opheus2 commented on Jan 27, 2026

    @opheus2
    Author

    This version worked @jaydrogers

    Image

    btw, I used serversideup/php-dev:628-8.4-fpm-nginx-trixie

  8. moved this from Backlog to Ready in serversideup/php: 5.0 Releaseon Jan 27, 2026
  9. jaydrogers commented on Jan 27, 2026

    @jaydrogers
    Member

    Awesome! I merged the change and it will be available the next release:

    I appreciate your ability to help test this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions