question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How to change the Context to other dir?

See original GitHub issue

The default context is . ,it’s the root dir,but if my Dockerfile is in ./alpine/Dockerfile,and my root dir include multiple Dockerfile,I get the docker image by git msg.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:9 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
CremaLucacommented, May 21, 2021

Solved: adding

- name: Checkout
  uses: actions/checkout@v2

At the beginning of the Github actions file

0reactions
CremaLucacommented, Jun 28, 2021

Solved: adding

- name: Checkout
  uses: actions/checkout@v2

At the beginning of the Github actions file

Can you share your file ,I add the check out ,it is also did not work

jobs:
  docker:
    runs-on: ubuntu-latest
    steps:
      - 
        name: Checkout
        uses: actions/checkout@v2
        with:
          fetch-depth: 0
      -
        name: Set up QEMU
        uses: docker/setup-qemu-action@v1
      -
        uses: docker/setup-buildx-action@v1
        id: builder1
      -
        uses: docker/setup-buildx-action@v1
        id: builder2
      -
        name: Login to DockerHub
        uses: docker/login-action@v1 
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}
      -
        name: Build and push 1
        id: docker_build1
        uses: docker/build-push-action@v2
        with:
          builder: ${{ steps.builder1.outputs.name }}
          context: ./app
          file: ./app/Dockerfile
          push: true
          tags: user/name-app:latest
      -
        name: Build and push 2
        id: docker_build2
        uses: docker/build-push-action@v2
        with:
          builder: ${{ steps.builder2.outputs.name }}
          context: ./web
          file: ./web/Dockerfile
          push: true
          tags: user/name-web:latest
Read more comments on GitHub >

github_iconTop Results From Across the Web

4.7. SELinux Contexts – Labeling Files
The chcon command changes the SELinux context for files. ... Run the chcon -R -t type directory-name command to change the type of...
Read more >
SELinux Change context of a file or directory (chcon ... - FreeKB
The most common way to permanently change the SELinux context of a file is to set the files parent directory to have the...
Read more >
How to copy SELinux context from one directory and apply it to ...
What I want to do is copy the SELinux context from an other user's /home directory and apply it to Tim's /websites directory....
Read more >
How can Bash execute a command in a different directory ...
... working directory cd /tmp : You use the builtins just like any other command, and can change directory context as many times...
Read more >
Changing Directory with a Python Context Manager
The context is disposed when the code is dedented. Using a context manager to change directories here would eliminate the relative path ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found