Coder Social home page Coder Social logo

wp-local-docker-images's Introduction

WP Local Docker Images

Images used by WP Local Docker

Support Level MIT License

Overview

Available on Dockerhub: 10up/phpfpm 10up/wpsnapshots

Support Level

Active: 10up is actively working on this, and we expect to continue work for the foreseeable future including keeping tested up to the most recent version of WordPress. Bug reports, feature requests, questions, and pull requests are welcome.

Like what you see?

Work with us at 10up

wp-local-docker-images's People

Contributors

brenoalvs avatar christianc1 avatar cmmarslender avatar eugene-manuilov avatar jeffpaul avatar jom avatar moraleida avatar tlovett1 avatar viper007bond avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

wp-local-docker-images's Issues

Add support for PHP 8.2

Is your enhancement related to a problem? Please describe.

add phpfm image for PHP 8.2

Designs

No response

Describe alternatives you've considered

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Add support for PHP 8.1

Is your enhancement related to a problem? Please describe.

Add phpfpm image for PHP 8.1

Designs

No response

Describe alternatives you've considered

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Add support for PHP 8.0

Is your enhancement related to a problem? Please describe.

Add phpfpm image for PHP 8.0

Designs

No response

Describe alternatives you've considered

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Alpine Linux, PHP-FPM and WordPress don't get along

Seeing if anyone has had any experience getting the official php:fpm-alpine image to work with wordpress. In my experience the PHP curl functions are not able to resolve DNS lookups, thus you commonly see messages in wp-admin exclaiming that wordpress was unable to check wordpress.org for updates.

I've search far and wide and not been able to find a solution. I figured if anyone knew it would be someone here.

Can all images live in a single repo?

Describe your question
We need to figure out if we can do all the images in the existing docker images repo or if we really need to separate them out.

Mariadb Support

I was curious to know if there is a plan to have a version of the '10updocker' container that uses MariaDB vs MySQL. The reason I ask is that there some new features included in 10.3 of MariaDB (temporal data tables) that are not supported in MySQL.

Thanks!
Brad

Readme updates

Is your enhancement related to a problem? Please describe.
It's not obvious the level of support provided for this repo, so let's add some clarification.

Describe the solution you'd like

  • add Active support level section and badge
  • add MIT license file and badge

Designs
n/a

Describe alternatives you've considered
n/a

Additional context
n/a

Update nginx-proxy for M1 Mac Support

Describe the bug
When the nginx-proxy container starts on an M1 Mac, you get the following error:

runtime: failed to create new OS thread (have 2 already; errno=22)
fatal error: newosproc

Steps to Reproduce

  1. Start the global containers
  2. Look at the Error in Docker Desktop

Expected behavior
The container should start without issue

Environment information

  • Device: MacBook Air (M1, 2020)
  • OS: MacOS 11.2.3

Additional context
The issue has been solved temporarily on the main repo nginx-proxy/nginx-proxy#1550

Update wpsnapshots image to use PHP 7.4/8.0

Describe the bug

https://hub.docker.com/r/10up/wpsnapshots is using php7.3 internally. This causes issues while running wpsnapshot pull command if the project contains php7.4+ code. This is because wpnsapshot includes wp-settings.php file as a part of testing MySQL connection.

Steps to Reproduce

  1. Create a fresh new site with 10uplocaldocker
  2. Create a snapshot and push it
  3. Clone vip-go-mu-plugins in wp-content using git clone [email protected]:Automattic/vip-go-mu-plugins-built.git mu-plugins.
  4. Pull the snapshot.
  5. You'll see an error like this:
✔ Global services are running...
✔ MariaDB has started...
Security Warning: WP Snapshots creates copies of your codebase and database. This could result in data retention policy issues, please exercise extreme caution when using production data.
This snapshot exists locally. Do you want to overwrite it with the remote copy? (y/N) y
Getting snapshot information...
Downloading snapshot (18.2 MB)...
<!DOCTYPE html>
<html lang="en-US">
<head>
        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
        <meta name="viewport" content="width=device-width">
                <meta name='robots' content='max-image-preview:large, noindex, follow' />
        <title>WordPress &rsaquo; Error</title>
        <style type="text/css">
                html {
                        background: #f1f1f1;
                }
                body {
                        background: #fff;
                        border: 1px solid #ccd0d4;
                        color: #444;
                        font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen-Sans, Ubuntu, Cantarell, "Helvetica Neue", sans-serif;
                        margin: 2em auto;
                        padding: 1em 2em;
                        max-width: 700px;
                        -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, .04);
                        box-shadow: 0 1px 1px rgba(0, 0, 0, .04);
                }
                h1 {
                        border-bottom: 1px solid #dadada;
                        clear: both;
                        color: #666;
                        font-size: 24px;
                        margin: 30px 0 0 0;
                        padding: 0;
                        padding-bottom: 7px;
                }
                #error-page {
                        margin-top: 50px;
                }
                #error-page p,
                #error-page .wp-die-message {
                        font-size: 14px;
                        line-height: 1.5;
                        margin: 25px 0 20px;
                }
                #error-page code {
                        font-family: Consolas, Monaco, monospace;
                }
                ul li {
                        margin-bottom: 10px;
                        font-size: 14px ;
                }
                a {
                        color: #0073aa;
                }
                a:hover,
                a:active {
                        color: #006799;
                }
                a:focus {
                        color: #124964;
                        -webkit-box-shadow:
                                0 0 0 1px #5b9dd9,
                                0 0 2px 1px rgba(30, 140, 190, 0.8);
                        box-shadow:
                                0 0 0 1px #5b9dd9,
                                0 0 2px 1px rgba(30, 140, 190, 0.8);
                        outline: none;
                }
                .button {
                        background: #f3f5f6;
                        border: 1px solid #016087;
                        color: #016087;
                        display: inline-block;
                        text-decoration: none;
                        font-size: 13px;
                        line-height: 2;
                        height: 28px;
                        margin: 0;
                        padding: 0 10px 1px;
                        cursor: pointer;
                        -webkit-border-radius: 3px;
                        -webkit-appearance: none;
                        border-radius: 3px;
                        white-space: nowrap;
                        -webkit-box-sizing: border-box;
                        -moz-box-sizing:    border-box;
                        box-sizing:         border-box;

                        vertical-align: top;
                }

                .button.button-large {
                        line-height: 2.30769231;
                        min-height: 32px;
                        padding: 0 12px;
                }

                .button:hover,
                .button:focus {
                        background: #f1f1f1;
                }

                .button:focus {
                        background: #f3f5f6;
                        border-color: #007cba;
                        -webkit-box-shadow: 0 0 0 1px #007cba;
                        box-shadow: 0 0 0 1px #007cba;
                        color: #016087;
                        outline: 2px solid transparent;
                        outline-offset: 0;
                }

                .button:active {
                        background: #f3f5f6;
                        border-color: #7e8993;
                        -webkit-box-shadow: none;
                        box-shadow: none;
                }

                        </style>
</head>
<body id="error-page">
        <div class="wp-die-message"><p>There has been a critical error on this website.</p><p><a href="https://wordpress.org/documentation/article/faq-troubleshooting/">Learn more about troubleshooting WordPress.</a></p></div></body>
</html>
        ✖

debug.log will show you this error:

[04-Jul-2023 11:27:23 UTC] PHP Parse error:  syntax error, unexpected 'array' (T_ARRAY), expecting function (T_FUNCTION) or const (T_CONST) in /var/www/html/wp-content/mu-plugins/healthcheck/class-healthcheck.php on line 18
[04-Jul-2023 11:27:23 UTC] PHP Notice:  Function is_embed was called <strong>incorrectly</strong>. Conditional query tags do not work before the query is run. Before then, they always return false. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.1.0.) in /var/www/html/wp-includes/functions.php on line 5865
[04-Jul-2023 11:27:23 UTC] PHP Stack trace:
[04-Jul-2023 11:27:23 UTC] PHP   1. WP_Fatal_Error_Handler->handle() /var/www/html/wp-includes/class-wp-fatal-error-handler.php:0
[04-Jul-2023 11:27:23 UTC] PHP   2. WP_Fatal_Error_Handler->display_error_template() /var/www/html/wp-includes/class-wp-fatal-error-handler.php:58
[04-Jul-2023 11:27:23 UTC] PHP   3. WP_Fatal_Error_Handler->display_default_error_template() /var/www/html/wp-includes/class-wp-fatal-error-handler.php:154
[04-Jul-2023 11:27:23 UTC] PHP   4. wp_die() /var/www/html/wp-includes/class-wp-fatal-error-handler.php:239
[04-Jul-2023 11:27:23 UTC] PHP   5. _default_wp_die_handler() /var/www/html/wp-includes/functions.php:3722
[04-Jul-2023 11:27:23 UTC] PHP   6. wp_robots() /var/www/html/wp-includes/functions.php:3798
[04-Jul-2023 11:27:23 UTC] PHP   7. apply_filters() /var/www/html/wp-includes/robots-template.php:32
[04-Jul-2023 11:27:23 UTC] PHP   8. WP_Hook->apply_filters() /var/www/html/wp-includes/plugin.php:205
[04-Jul-2023 11:27:23 UTC] PHP   9. wp_robots_noindex_embeds() /var/www/html/wp-includes/class-wp-hook.php:308
[04-Jul-2023 11:27:23 UTC] PHP  10. is_embed() /var/www/html/wp-includes/robots-template.php:93
[04-Jul-2023 11:27:23 UTC] PHP  11. _doing_it_wrong() /var/www/html/wp-includes/query.php:882
[04-Jul-2023 11:27:23 UTC] PHP  12. trigger_error() /var/www/html/wp-includes/functions.php:5865
[04-Jul-2023 11:27:23 UTC] PHP Notice:  Function is_search was called <strong>incorrectly</strong>. Conditional query tags do not work before the query is run. Before then, they always return false. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.1.0.) in /var/www/html/wp-includes/functions.php on line 5865
[04-Jul-2023 11:27:23 UTC] PHP Stack trace:
[04-Jul-2023 11:27:23 UTC] PHP   1. WP_Fatal_Error_Handler->handle() /var/www/html/wp-includes/class-wp-fatal-error-handler.php:0
[04-Jul-2023 11:27:23 UTC] PHP   2. WP_Fatal_Error_Handler->display_error_template() /var/www/html/wp-includes/class-wp-fatal-error-handler.php:58
[04-Jul-2023 11:27:23 UTC] PHP   3. WP_Fatal_Error_Handler->display_default_error_template() /var/www/html/wp-includes/class-wp-fatal-error-handler.php:154
[04-Jul-2023 11:27:23 UTC] PHP   4. wp_die() /var/www/html/wp-includes/class-wp-fatal-error-handler.php:239
[04-Jul-2023 11:27:23 UTC] PHP   5. _default_wp_die_handler() /var/www/html/wp-includes/functions.php:3722
[04-Jul-2023 11:27:23 UTC] PHP   6. wp_robots() /var/www/html/wp-includes/functions.php:3798
[04-Jul-2023 11:27:23 UTC] PHP   7. apply_filters() /var/www/html/wp-includes/robots-template.php:32
[04-Jul-2023 11:27:23 UTC] PHP   8. WP_Hook->apply_filters() /var/www/html/wp-includes/plugin.php:205
[04-Jul-2023 11:27:23 UTC] PHP   9. wp_robots_noindex_search() /var/www/html/wp-includes/class-wp-hook.php:308
[04-Jul-2023 11:27:23 UTC] PHP  10. is_search() /var/www/html/wp-includes/robots-template.php:119
[04-Jul-2023 11:27:23 UTC] PHP  11. _doing_it_wrong() /var/www/html/wp-includes/query.php:700
[04-Jul-2023 11:27:23 UTC] PHP  12. trigger_error() /var/www/html/wp-includes/functions.php:5865

This error came because https://github.com/Automattic/vip-go-mu-plugins-built/blob/master/healthcheck/class-healthcheck.php#L18 has a php7.4 syntax

Screenshots, screen recording, code snippet

No response

Environment information

No response

WordPress information

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

latest nginx-proxy container broken

Since #15 was merged on the 18th, new docker builds were triggered which broke the nginx-proxy container. starting 10up/nginx-proxy:latest results in this error:

2019/09/20 19:34:06 [emerg] 66#66: SSL_CTX_use_certificate("/etc/nginx/certs/default.crt") failed (SSL: error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small)
nginx: [emerg] SSL_CTX_use_certificate("/etc/nginx/certs/default.crt") failed (SSL: error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small)

It appears to be related to this change nginx-proxy/nginx-proxy@3a9de2d on the base container.

I have a workaround that involves using :0.7.0 rather than :latest for the base nginx container. I feel like we should always be using a specifically tagged version on the base containers to prevent this kind of stuff in the future

Add support for PHP 7.4

Is your enhancement related to a problem? Please describe.

Adds phpfpm image for PHP 7.4

Designs

No response

Describe alternatives you've considered

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

PHP 7.2

Could you please add support for PHP 7.2?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.