-
Notifications
You must be signed in to change notification settings - Fork 200
Issues: GoogleContainerTools/container-structure-test
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
--pull output appears in --test-report
enhancement
help wanted
#245
opened Feb 25, 2020 by
reschenburgIDBS
Exposed Ports Metadata test fails if the protocol is specified.
bug
help wanted
#240
opened Dec 31, 2019 by
richnusgeeks
In v2.MetadataTest,
envVar
property is actually env
bug
help wanted
#230
opened Aug 17, 2019 by
zephinzer
Setup in command test fails to create dir or touch file
help wanted
question
#227
opened Aug 1, 2019 by
vishalsangave
podman support for commands test
enhancement
help wanted
question
#225
opened Jul 9, 2019 by
parul1593
Running container_test in bazel can't be cached
bug
good first issue
help wanted
#184
opened Nov 23, 2018 by
Monnoroch
Refactor test runner to remove shared boilerplate between test types
enhancement
help wanted
#148
opened Jun 8, 2018 by
nkubala
Add support for running container-structure-test inside gVisor
enhancement
help wanted
#125
opened May 2, 2018 by
nkubala
Metadata Test should support all fields from ContainerConfig
enhancement
help wanted
#80
opened Mar 9, 2018 by
dzavalkinolx
Output of list with empty string is the same to empty list
bug
good first issue
help wanted
#79
opened Mar 9, 2018 by
dzavalkinolx
Feature request: support copyfile from local to container
enhancement
help wanted
#73
opened Mar 1, 2018 by
wanghaoran1988
Passing arguments to the docker run command
enhancement
help wanted
#70
opened Feb 26, 2018 by
mogthesprog
apt-get command's args do not have "help", have "--help"
enhancement
help wanted
#29
opened Jan 12, 2018 by
Urotea
ProTip!
Follow long discussions with comments:>50.