Posts by monsen

  • Trying to create Image with Dockerfile in compose plugin

    I am trying to create an image of "erseco/alpine-php-webserver" including composer (https://hub.docker.com/r/erseco/alpine-php-webserver)


    The documentation says to build an image using the following Dockerfile:


    Docker
    FROM erseco/alpine-php-webserver:latest
USER root
# Install composer from the official image
RUN apk add --no-cache composer
USER nobody
# Run composer install to install the dependencies
RUN composer install --optimize-autoloader --no-interaction --no-progress


    Which i did in the OMV compose plugin without success.

    It throws out the following error:


    Code
    500 - Internal Server Error
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; docker build --progress plain --tag 'erseco/alpine-php-webserver_composer' '/srv/dev-disk-by-label-SSD_Data/appdata/YAML_Storage/erseco/alpine-php-webserver_composer/' 2>&1': #0 building with "default" instance using docker driver #1 [internal] load build definition from Dockerfile #1 transferring dockerfile: 488B done #1 DONE 0.0s #2 [internal] load metadata for docker.io/erseco/alpine-php-webserver:latest #2 DONE 0.0s #3 [internal] load .dockerignore #3 transferring context: 2B done #3 DONE 0.0s #4 [1/3] FROM docker.io/erseco/alpine-php-webserver:latest #4 DONE 0.0s #5 [2/3] RUN apk add --no-cache composer #5 CACHED #6 [3/3] RUN composer install --optimize-autoloader --no-interaction --no-progress #6 0.178 Composer could not find a composer.json file in /var/www/html #6 0.178 To initialize a project, please create a composer.json file. See https://getcomposer.org/basic-usage #6 ERROR: process "/bin/sh -c composer install --optimize-autoloader --no-interaction --no-progress" did not complete successfully: exit code: 1 ------ > [3/3] RUN composer install --optimize-autoloader --no-interaction --no-progress: 0.178 Composer could not find a composer.json file in /var/www/html 0.178 To initialize a project, please create a composer.json file. See https://getcomposer.org/basic-usage ------ Dockerfile:13 -------------------- 11 |...


    So in general i think it says that the composer.json file is missing?


    Anyone got an idea what i need to do?

  • Hard drive showing twice in drive dashboard

  • Hard drive showing twice in drive dashboard

    Funnily the issue is back.


    Code
    root@debnas:~# blkid
/dev/sdd1: LABEL="DataHitachi" UUID="a72f1874-5021-4f68-aa17-710a7c414e27" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="4f027152-069d-413b-a000-92498dfc7c4a"
/dev/sdb4: SEC_TYPE="msdos" UUID="0D28-D1AD" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI-system" PARTUUID="7ac9cf10-0660-4f56-afdc-8f0f45dee223"
/dev/sdb5: UUID="cd074168-ed5e-4307-9c61-c7554ebb5a0a" TYPE="swap" PARTLABEL="Linux swap" PARTUUID="0f556396-a277-4dac-99ae-be9f700d30f0"
/dev/sdb3: LABEL="SSD_Data" UUID="6c9a3447-9243-47ef-84f8-69205fe4a1a2" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="8b5e162a-f695-49f1-8a50-b3df87d7c117"
/dev/sdb1: UUID="a72f30ef-09bd-4b1f-9f55-1122f120cab6" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="112020c8-8a26-4bb9-a781-883a9cfea18c"
/dev/sdc1: LABEL="DataWD" UUID="c0a24e86-363b-412d-ade9-c1c01a2ab6de" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="646f2de2-2633-41ec-86f2-41fc93142f26"
/dev/sda1: LABEL="ParityWD" UUID="fdcaae30-3efb-47a7-bab3-a0b78987c8d9" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="a918b332-de56-4c45-8834-c1268ee4753d"
/dev/sdb2: PARTLABEL="BIOS boot partition" PARTUUID="dfe26bcf-a05d-4ad0-91eb-1754f3fae17e"

  • Error docker compose plugin

    Then scroll up again. You missed that i am inviting you for beers ;)


    Quote from ryecoaaron
    You must have had a second omv-engined process running and plugins being updated don't kill it. The reboot did but my killall line would've done that too.


    Do i need to investigate that multiple omv-engined are started or is that usual behaviour?

  • Error docker compose plugin

    But you can see the screen i copied you a screenshot above, no?


    Just copy pasted the sudo. I know i dont need it but it doesnt hurt i guess ;)


    Well after all it seems to be ok again. Not sure why it did not any earlier. Seems like a reboot was needed.


    AND: thanks man! As always you have been a great help. I think i owe you a beer or two ;)

    Where are you located? US?

  • Error docker compose plugin

    Quote from ryecoaaron

    You never made that clear. I thought you were still having the showenv error. This is why I need full error messages. If there isn't a good error message, you will need to put your system in debug mode and then try to navigate to the plugin to see if a helpful error message is generated.


    sudo monit stop omv-engined

    sudo omv-engined -df


    Well it looks to me if the error is still the same. See above. I am doing my best.


    I did what you proposed. I assume i will see the error messages in CLI then? In that case there is nothing to be seen. I clicked around in the compose plugin after the CLI commands to generate errors.


    Code
    root@debnas:~# sudo monit stop omv-engined
root@debnas:~# sudo omv-engined -df
omv-engined[631355]: Daemon already running (pid=10123)
omv-engined[631355]:
Daemon already running (pid=10123)
root@debnas:~#

  • Error docker compose plugin

    Code
    Statusinformationen werden eingelesen… Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
root@debnas:~# sudo omv-confdbadm migrate "conf.service.compose" "7.2.8"
  Running migration conf.service.compose_7.2.8
root@debnas:~# sudo omv-mkworkbench all
root@debnas:~# sudo omv-confdbadm migrate "conf.service.compose" "7.2.8"
  Running migration conf.service.compose_7.2.8


    No, that did not help.

  • Error docker compose plugin

  • Error docker compose plugin

    I hit ctrl-shift-R and to make sure i clean the browser cache. Then close tab. Relogin. Same error


    And just to make double-sure i tried from a different machine with a different browser. Same result