nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

No logs from scripts when using custom docker image

Kamil_g18jdi

Hi I'm having an issue when logs are not showing for all scripts within the step that uses custom docker image.

The custom image is created from official php-fpm:7.2 docker image. When running the official image script output is visible. I've reviewed the Dockerfile, but I can't see a reason why it would change behaviour.

Any ideas where I can look to find the source of the problem?

Accepted answers

Kamil_g18jdi

The source of my problems was the fact that the newly created user didn't have write permissions in his home folder.

This solves all of my problems.

All comments

Kamil_g18jdi

This is how it looks in the pipeline console.
This pipeline contained simple step: 'echo test'.

I can tell that all scripts are run as artifacts are created as well it can proceed to the next step

ktomk

Welcome to the Atlassian Community.

On first glance at least for me this is not so easy to answer.

Maybe you can share the complete name of the container image? Just because php-fpm:7.2 is not found by the Atlassian Bitbucket Cloud Pipelines Plugin so what you write about I can not easily reproduce; gives the following error:

rpc error: code = Unknown desc = failed to resolve image "docker.io/library/php-fpm:7.2": no available registry endpoint: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

Sharing all the relevant parts of your bitbucket-pipelines.yml might also not be a bad idea next to your screenshot.

Regarding that screenshot you posted:

When you extend the "Build setup" section (and also the "Build teardown" section), what does it show?

I ask because I had a similar issue (like "no logs from script") and it showed an error message therein. Compare with the screenshot / infos in the question Pipeline Build Setup: /bin/sh: /usr/bin/mkfifo: not found.

It was with a different image (not ???/php-fpm:7.2 but docker.io/busybox) and I could resolve the issue with a little modification of the image. Your mileage may vary.

Kamil_g18jdi

Hi. Thanks for your response and sorry for not enough information included in my post.

I've put mistake in docker image I referenced its: 'php:7.2-fpm'. From that image I create another one called 'kingfisherdirect/magento2-php:2', which Dockerfile you can find here: https://bitbucket.org/kingfisherdirect/docker-magento2-php/src/v2/Dockerfile.

For this issue I created a small public repository which shows issue without anything else.

https://bitbucket.org/kamil-kingfisher/docker-pipeline-test/addon/pipelines/home#!/results/1/steps/%7B8162f12c-ebed-41ba-bdc5-f18ac2b0224b%7D

ktomk

Sorry for not being able to reply earlier. I couldn't find anything specific for which I could say this is it.

What caught my attention is that in the entry-point of your custom image, `$@` is not quoted with `exec` at the end:

I would change that to quoted:

exec "$@"

Maybe it helps. I was looking into the entry-point related parts of the Dockerfiles first.

Kamil_g18jdi

The source of my problems was the fact that the newly created user didn't have write permissions in his home folder.

This solves all of my problems.

ktomk

Thanks for sharing the solution. I didn't thought about that.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket

bitbucket-pipelines