You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Status: Downloaded newer image for php:7.2-rc-fpm ---> 008dcb3cc91c Step 2/12 : RUN apt-get update \ && apt-get install -y \ libfreetype6-dev \ libjpeg62-turbo-dev \ libmemcached-dev \ libpng12-dev \ sendmail \ && docker-php-ext-configure gd --with-freetype-dir=/usr/include/ --with-jpeg-dir=/usr/include/ \ && docker-php-ext-install gd mbstring mcrypt pdo pdo_mysql \ && pecl install xdebug \ && doc
I have issues connecting to the mysql database spawned by this docker container. I ger repeated access denied errors. I tried multiple ways: use nsenter to enter the mysql container and then the mysql client to connect as root or as user (as configured with the environment variables): nsenter --target $(docker inspect --format {{.State.Pid}} etc_mysql_1) --mount --uts --ipc --net --pid /bin/bash u
From our docs description of onbuild: While the onbuild variant is really useful for "getting off the ground running" (zero to Dockerized in a short period of time), it's not recommended for long-term usage within a project due to the lack of control over when the ONBUILD triggers fire (see also docker/docker#5714, docker/docker#8240, docker/docker#11917). Users are often wanting customization on
mysql> show slave status\G; *************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: 10.254.30.104 Master_User: repl Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysqld-bin.000004 Read_Master_Log_Pos: 120 Relay_Log_File: mysqld-relay-bin.000003 Relay_Log_Pos: 64342 Relay_Master_Log_File: mysqld-bin.000001 Slave_IO_Running:
diff --git a/_bashbrew-list b/_bashbrew-list index d46c22d..eff342a 100644 --- a/_bashbrew-list +++ b/_bashbrew-list @@ -28,21 +28,21 @@ node:6.10.3-alpine node:6.10.3-onbuild node:6.10.3-slim node:6.10.3-wheezy -node:7 -node:7-alpine -node:7-onbuild -node:7-slim -node:7-wheezy -node:7.10 -node:7.10-alpine -node:7.10-onbuild -node:7.10-slim -node:7.10-wheezy -node:7.10.0 -node:7.10.0-alpine -node:
I recently completed a project that populated the database with UTF8 encoded text. My script was able to create the database using the correct character-set, but the text data could not be properly imported. Apparently, the initdb scripts are assumed to be ascii encoded, so I had to make a minor modification to docker-entrypoint.sh. mysql=( mysql --protocol=socket --default_character_set=utf8 -uro
diff --git a/node_alpine/Dockerfile b/node_alpine/Dockerfile index e011856..19db13f 100644 --- a/node_alpine/Dockerfile +++ b/node_alpine/Dockerfile @@ -43,4 +43,20 @@ RUN adduser -D -u 1000 node \ && rm -Rf "node-v$NODE_VERSION" \ && rm "node-v$NODE_VERSION.tar.xz" SHASUMS256.txt.asc SHASUMS256.txt +ENV YARN_VERSION 0.21.3 + +RUN apk add --no-cache --virtual .build-deps-yarn curl gnupg \ + && for
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く