fly deploy --remote-only ignores the custom .dockerignore file

Open
#3,228 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, go
Domain
cli

Research direction

Start by reproducing fly deploy --remote-only with --ignorefile when a custom ignore file is in a subdirectory and .dockerignore is in the root. Trace which ignore file flyctl selects; done means the specified custom file is used instead of the root .dockerignore.

Written by the indexing model from the issue text.

Description

bug

Please only report specific issues with flyctl behavior. Anything like a support request for your application should go to https://community.fly.io. More people watch that space and can help you faster!

Describe the bug
I’m using fly deploy --ignorefile to point it to the ignore files but still all my files are uploaded to the server. However, if I specify a custom dockerignore in a sub-directory, and have a .dockerignore in the root directory, it doesn’t use the one I specified but rather the .dockerignore in the root directory. I think this is an issue with flyctl.

  • MacOS
  • flyctl 0.1.147

** Paste your fly.toml

# paste your config file here

** Command output: **

# paste command output here
Dominant language
Go
Stars
1.7k
Forks
311
Avg merge
12h 50m
Merged PRs (30d)
78

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from superfly/flyctl

All issues in superfly/flyctl

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.